-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.4.6
-
Component/s: None
-
Fully Compatible
-
ALL
-
v5.0, v4.4
-
-
Sharding 2021-06-14
-
(copied to CRM)
On a MongoDB v4.4.1+ sharded cluster, when a secondary is taken down, certain operations that should succeed result in an error from the server when the connection string includes readPreference=secondary&maxStalenessSeconds=90.
The error looks to be a result of SERVER-50170, specifically this new check.
- is depended on by
-
NODE-3136 "Incompatible wire version" error with MongoDB 4.4 secondary reads when a secondary goes down
- Closed
- is related to
-
SERVER-50170 Fix server selection failure on mongos
- Closed