-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Client, Sharding
-
None
-
Environment:All OSes except 32-bit windows, which has a different polling interface.
-
ALL
When a host fails cleanly or connections are broken by keepalive failures, we should respond to OS-level info about connection state and clear these connections before using from the pool.
- duplicates
-
SERVER-5793 connection pools in mongos and mongod don't check idle connections until used
- Closed
- is depended on by
-
SERVER-7008 socket exception [SEND_ERROR] on Mongo Sharding
- Closed
-
SERVER-4706 when a socket between mongos and mongod fails, close all connections immediately
- Closed
-
SERVER-10261 Disable SSL session caching on server to avoid Java driver SSL connection problems
- Closed
- is duplicated by
-
SERVER-9908 On Linux, Socket::connect() timeout doesn't interrupt ConnectBG job
- Closed
- is related to
-
SERVER-4997 Mongos not clearing stale connections
- Closed
-
SERVER-5793 connection pools in mongos and mongod don't check idle connections until used
- Closed
-
SERVER-7743 Print the low-level error when socket operations fail
- Closed
- related to
-
SERVER-4706 when a socket between mongos and mongod fails, close all connections immediately
- Closed