Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Won't Do
-
5.1.0, 5.0.2
-
None
-
ALL
-
v5.0
-
Sharding EMEA 2021-09-06
-
144
Description
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.
Attachments
Issue Links
- 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
-