-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.3.1
-
Component/s: Internal Client
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
DBClientReplicaSet currently manages it's own connections to the replica set members. And because of this, the connections used by each DBClientRS are visible, making it hard for other objects to reuse the same connections when they are idle, and makes it hard for mongos to take account of all the outgoing connections. This setup also causes the DBClientRS to create and destroy more connections more than it should if it were using a connection pool.
- duplicates
-
SERVER-9788 mongos does not re-evaluate read preference once a valid replica set member is chosen
-
- Closed
-
- is depended on by
-
SERVER-9984 MongoS spawns new connections to secondaries after each change of readPreference tags
-
- Closed
-
- is related to
-
-
- Closed
-