-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding, Testing Infrastructure
-
Fully Compatible
-
v3.6
-
Sharding 2017-10-02, Sharding 2017-10-23, Sharding 2017-11-13, Sharding 2017-12-04, Sharding 2018-01-01, Sharding 2018-01-15, Sharding 2017-12-18
-
0
Update the jstests/concurrency/fsm_all_sharded_with_stepdowns.js and jstests/concurrency/fsm_all_sharded_with_stepdowns_and_balancer.js files to specify
{
sharded: {enabled: true, stepdownOptions: {configStepdown: true, shardStepdown: true}},
replication: {enabled: true}
}
as the cluster options. Since mongos won't automatically retry any operations destined for the shards, we'll want to additionally load() the jstests/libs/override_methods/auto_retry_on_network_error.js override from SERVER-30953 when shardStepdown=true inside of worker_thread.js similar to what's done for implicitly retrying on "DatabaseDropPending" error responses.
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-