-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
3
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Currently, stepdown resiliency for sharded cluster are tested by:
- sharding_csrs_continuous_config_stepdown:
- Covers only jstests/sharding/** tests
- Only step down config server
- concurrency_sharded_with_stepdowns:
- Covers only FSM tests
- step down all primaries, both config and shard
Unfortunately, I can't find any suite that is covering our most basic tests ( "jstests/core/*") using a sharded cluster with stepdowns.
We have something similar for other cluster topology, but not for sharded clusters:
- retryable_writes_jscore_stepdown_passthrough
- tenant_migration_stepdown_jscore_passthrough
- shard_split_stepdown_jscore_passthrough
- is depended on by
-
SERVER-97627 Ensure the existence of one or more test suites executing the content of 'core_sharding' and provisioning a 2-shard cluster
-
- Closed
-
- is related to
-
SERVER-97627 Ensure the existence of one or more test suites executing the content of 'core_sharding' and provisioning a 2-shard cluster
-
- Closed
-
-
SERVER-99475 countDocuments() returns a CursorNotFound error when one of the queried shards is restarted
-
- Needs Scheduling
-