-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
Cluster Scalability 2024-10-28
-
0
The concurrency suites with balancer and failovers previously set this value (see SERVER-90217) but the parameter was removed in SERVER-94696. Not setting this parameter in the suite results in a default value of one second (set here or here). The default value of one second is too short as it can result in inconsistent secondary reads as described in SERVER-87673. The concurrency suites with balancers and failover should re-set this value again to avoid intermittent test failures from inconsistent secondary reads.
- is caused by
-
SERVER-94696 Collapse kill, terminate and stepdown concurrency sharded with balancer suites
- Closed
- related to
-
SERVER-90217 Consider setting orphanCleanupDelaySecs on suites with balancer and failovers
- Closed