-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Networking & Observability
-
Fully Compatible
-
ALL
-
N&O 2026-01-05
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This is causing BF-40936. Before SERVER-115387, ContinuousStepdown was mistakenly not enabled for ShardingTests. Now that it is, the sharding/network/rsm_horizon_change.js is failing because it expects the primary not to change throughout the test. The replSetReconfig command will fail if not sent to the primary.
- is related to
-
SERVER-115387 The sharding_csrs_continuous_config_stepdown suite does not actually trigger stepdown events
-
- Closed
-