-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ClusterScalability Dec22-Jan5, ClusterScalability Jan5-Jan19
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
It is possible that several commands that rely on CSRS primary fail with FailedToSatisfyReadPreference if CSRS primary is not available for a long time due to stepdown. This can happen more frequently in slow variants. This error is not a network error or retriable error and client is expected to retry it. We should add a default override for sharding_csrs_config_stepdown suite where we retry commands on this error.
- related to
-
SERVER-118448 Make sharding_csrs_continuous_config_stepdown use a larger defaultFindReplicaSetHostTimeoutMS and fassertOnLockTimeoutForStepUpDown when running on slow build variants
-
- Closed
-