[SERVER-5793] connection pools in mongos and mongod don't check idle connections until used Created: 09/May/12  Updated: 11/Jul/16  Resolved: 29/Jan/14

Status: Closed
Project: Core Server
Component/s: Networking, Sharding
Affects Version/s: None
Fix Version/s: 2.5.5

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Unassigned
Resolution: Done Votes: 10
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-9041 proactively detect broken connections... Closed
Related
related to SERVER-9041 proactively detect broken connections... Closed
related to SERVER-11681 Mongos cleanup and integration of wri... Closed
Operating System: ALL
Participants:

 Description   

This leads to the case where a server goes down and comes back up, and hours later a socket exception occurs b/c the connection was never used previously.

EDIT:
This is addressed by SERVER-9041 (proactively checking idle connections in the pool) and SERVER-11681 (no longer holding thread-local connections in mongos between requests)


Generated at Thu Feb 08 03:09:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.