[SERVER-20982] Add concurrency workload framework to triggers various node failovers Created: 16/Oct/15 Updated: 06/Dec/22 Resolved: 09/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||||||||||||||
| Sprint: | Sharding B (10/30/15), Sharding D (12/11/15), Sharding E (01/08/16) | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
We'd like to introduce a concurrency/FSM workload that triggers config server failovers to verify that they occur transparently to clients. Basic implementation notes:
Here's what a schedule looks like now:
Here's what the schedule should look like after:
|
| Comments |
| Comment by Kamran K. [ 18/Feb/16 ] |
|
I think this task is still worthwhile for a few reasons: Judah and Esha wrote code to expose cluster connections and add background workloads to the FSM suite, so I think it's less than a day of work to write a basic workload that steps down the CSRS primary periodically. That would at least give us an idea about whether we can expect to find new bugs with this approach (before deciding if it's worth adding as a permanent suite, making it robust for Evergreen, etc.). |
| Comment by Spencer Brody (Inactive) [ 09/Feb/16 ] |
|
This seems like most of the test coverage we were hoping to get with this are being obtained through I propose closing this ticket as a duplicate of those - kamran.khan, what do you think? |