-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.3.1
-
Component/s: Internal Client, Sharding
-
None
-
ALL
The problem here is that when using replica set connections it is possible for mongos to use a different connection when setting the shard version and actually performing the query because of read preference. This means that the actual connection used when performing a query will be completely unversioned, totally bypassing the stale config version checking in the shard.
- is duplicated by
-
SERVER-7089 connection churn from mongos to mongod
- Closed
- related to
-
SERVER-6989 mongodump segfaults when host is passed a replSet string
- Closed
-
SERVER-10904 Possible for _master and _slaveConn to be pointing to different connections even with primary read pref
- Closed