[SERVER-35427] Add sharded rollback tests Created: 05/Jun/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication, Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Participants: |
| Description |
|
We don't do any testing specifically of rollbacks in sharding. Sharding can do special writes so we should make sure they get timestamped and rolled back correctly. A sharded rollback fuzzer that adds sharding metadata commands to the grammar would be interesting. A sharded kill_nodes suite that kills primaries and secondaries in config servers and shards would also be useful. Simply doing a sharded kill_primaries or kill_secondaries suite would go a long way. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |