[SERVER-5632] Add a way to flush all connections in the connection pools Created: 17/Apr/12  Updated: 10/Dec/14  Resolved: 06/Oct/14

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

Type: Improvement Priority: Major - P3
Reporter: Greg Studer Assignee: Randolph Tan
Resolution: Done Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File pooling_no_reset.js    
Issue Links:
Depends
Duplicate
is duplicated by SERVER-8812 connPoolStats and connPoolSync should... Closed
Related
is related to SERVER-5587 Command to close current connections Closed
Participants:

 Description   

For debugging issues related to the connection pool, it would often be useful to be able to flush all those connections, similar to the way we flush config data currently. A command would make it clear whether the network is a problem (breaking connections over time) versus a problem storing stale connections in a mongo process.

Additionally, it would be helpful to be able to flush replica set information.



 Comments   
Comment by Greg Studer [ 06/Oct/14 ]

As of v2.6, all connections not in the pool are in active use by operations and so are correctly not eligible for clearing. The pool is reset via the "connPoolSync" command.

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