[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: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| 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. |