[SERVER-21054] Add failover workload to cause CSRS config server primary unavailability Created: 21/Oct/15  Updated: 06/Dec/22  Resolved: 27/Jan/16

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev 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:
Depends
depends on SERVER-20982 Add concurrency workload framework to... Closed
Related
related to SERVER-22081 Enable CSRS continuous stepdown workl... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Sprint: Sharding B (10/30/15), Sharding C (11/20/15), Sharding D (12/11/15), Sharding E (01/08/16)
Participants:

 Comments   
Comment by Spencer Brody (Inactive) [ 27/Jan/16 ]

Given that we're already running the sharding suite with continuous config server stepdown per SERVER-22081, we decided that adding a similar continuous config server stepdown workload to the concurrency suite likely won't gain us a meaningful increase in test coverage, and since it's a non-trivial amount of work to make stable, we won't do it.

Comment by Kaloian Manassiev [ 22/Oct/15 ]

"State" in this case refers to the states in the Finite State Machine testing framework under jstests/concurrency. Given that this is a title of a ticket, workload seems like a more appropriate title, so I have changed it.

Comment by Andy Schwerin [ 21/Oct/15 ]

Add a failover state to what?

Generated at Thu Feb 08 03:56:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.