-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Currently there's a map in s/shard_version.cpp that associated each client connection with a shard version. Might be better to store that version in each thread's thread-local ClientBase object.
- related to
-
SERVER-7460 Issue with threads re-using previously released memory containing a Shard version
-
- Closed
-
-
SERVER-1714 multiplex mongos -> mongod connecions after successful read op
-
- Closed
-