[SERVER-13374] change connection pool cleanup limit Created: 27/Mar/14  Updated: 11/Jul/16  Resolved: 31/Mar/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.6.0-rc3

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

Issue Links:
Related
Participants:

 Description   

With the changes in 2.6, we rely more heavily on the connection pool and so the default size limits are no longer appropriate and can cause connection thrashing.

We should change the default to rely on the standard connection pool cleanup mechanisms in most cases, and not destroy connections over the limit.



 Comments   
Comment by Githook User [ 31/Mar/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-13374 change connection pool defaults
(cherry picked from commit f71610672b0506b233a449bfafb303497c97ae50)
Branch: v2.6
https://github.com/mongodb/mongo/commit/a12d09c9757301c3872cf4b45027d287e3dcc366

Comment by Githook User [ 31/Mar/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-13374 change connection pool defaults
Branch: master
https://github.com/mongodb/mongo/commit/f71610672b0506b233a449bfafb303497c97ae50

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