[SERVER-33887] Add a test suite that kills primaries and secondaries Created: 14/Mar/18 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication, Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Engineering Test | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | MaxH, sharding-nyc-test-improvements | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Cluster Scalability
|
||||
| Backport Requested: |
v3.6
|
||||
| Participants: | |||||
| Description |
|
We could also add in force step downs with no catchup period. This will use retryable writes since the primary is being killed, but provide maximum chaos and rollback scenarios. This can be done with a single replica set and with a sharded cluster. |
| Comments |
| Comment by Kaloian Manassiev [ 09/May/19 ] |
|
While having a "chaos" kind of testing is a great idea, it requires a little bit more thought than just a ticket. max.hirschhorn, is there some Epic about this kind of testing where we can put this ticket? |