-
Type: Bug
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.1.0, 5.0.2
-
Component/s: Sharding
-
ALL
-
v5.0
-
Sharding EMEA 2021-09-06
-
144
If the RSM on any node times out while trying to discover a new primary host, we could throw FailedToSatisfyReadPreference. We should account for that error in this test.
- is related to
-
SERVER-60706 Retry FailedToSatisfyReadPreference errors while performing retryable writes
- Backlog
- related to
-
SERVER-59409 Race between reconfig replication and stepup can cause RSM to be stuck in reporting ReplicaSetNoPrimary
- Closed