[SERVER-33884] Add retryable writes to kill secondaries suite Created: 14/Mar/18  Updated: 06/Dec/22  Resolved: 02/Aug/19

Status: Closed
Project: Core Server
Component/s: Sharding, Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-33879 config.transactions is not updated du... Closed
Assigned Teams:
Sharding
Backport Requested:
v3.6
Participants:

 Description   

This will test that we correctly fix up the transactions table on recovery mid-batch. This would likely have caught SERVER-33879.



 Comments   
Comment by Kaloian Manassiev [ 02/Aug/19 ]

We don't think that such a suite will catch any bugs that killing the primary won't.

Comment by Daniel Gottlieb (Inactive) [ 04/Apr/18 ]

More information: SERVER-32323 turned on writing to config.transactions as part of transactions (which completely broke the kill secondary task). I don't think it's critical to add any specialized testing for 4.0. But if something is made for the 3.6 branch, it might as well live in 4.0 as well.

Comment by Judah Schvimer [ 14/Mar/18 ]

This test suite can still run with w:1, which will be different from the other retyable writes passthroughs.

Generated at Thu Feb 08 04:34:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.