-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.0.9, 3.2.13, 3.4.4
-
Component/s: Sharding
-
None
-
ALL
-
-
Sharding 11 (03/11/16), Sharding 2017-08-21
-
(copied to CRM)
-
0
SecondaryPreferred reads are allowed to be routed to a primary host if this is deemed the most appropriate.
Legacy style queries disable the version checking and so they go over unversioned connections. However other command implementations, such as distinct or count which use ShardCollection will fail with a cryptic NodeNotFound error if they get routed to a primary with the SecondaryPreferred preference set, because they do not expect to see StaleConfigException.
See the included repro script for more information.
- related to
-
SERVER-18671 SecondaryPreferred can end up using unversioned connections
- Closed