-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
ALL
Currently, mongos closes one connection at a time, even though it can "tell" that every connection to that shard is going to be bad. It could mark them all as failed and so not return as many error to the client.
Leads to Assertion: 13633:error querying server errors (for Google-ability).
- depends on
-
SERVER-9041 proactively detect broken connections detected by the network
- Closed
- is duplicated by
-
SERVER-4997 Mongos not clearing stale connections
- Closed
- is related to
-
SERVER-9041 proactively detect broken connections detected by the network
- Closed
-
SERVER-7573 Add tests for network connectivity loss, especially in sharded systems.
- Closed
- related to
-
SERVER-9788 mongos does not re-evaluate read preference once a valid replica set member is chosen
- Closed
-
SERVER-7629 Make DBClientReplicaSet draw connections from a pool
- Closed