[SERVER-29237] Add maxConnecting in asio connpool Created: 16/May/17 Updated: 30/Oct/23 Resolved: 02/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.15, 3.4.6, 3.5.9 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v3.4, v3.2
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Platforms 2017-05-29, Platforms 2017-06-19 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Issue Status as of Jun 15, 2017 ISSUE DESCRIPTION RATIONALE
It is possible for mongos nodes to overwhelm the primary with connection requests, which may have adverse consequences. The ShardingTaskExecutorPoolMaxConnecting flag allows users to limit the rate at which mongos nodes add connectons to connection pools. The flag changes mongos behavior so that only N connections can be in the processing state at any one time (in setup/refresh) to avoid overwhelming mongod nodes with connection requests. It is worth noting that this flag is per connection pool, so if a mongos node has C connection pools and ShardingTaskExecutorPoolMaxConnecting is set to N, the node may establish up to C * N connections to a mongod in a scenario like the one described above. Please see The default value is unlimited for backwards-compatibility purposes. This default value may change in future versions of MongoDB. SUPPORTED VERSIONS Original descriptionA new connection pool option which controls that rate at which we add new connections. It changes behavior so that only N connections can be in the processing state at any one time (in setup/refresh). More connections will be added, if needed, as each new connection completes, fails or times out. Available in mongos via ShardingTaskExecutorPoolMaxConnecting, defaults to unlimited. |
| Comments |
| Comment by Githook User [ 15/Jun/17 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: A new connection pool option which controls that rate at which we add available in mongos via ShardingTaskExecutorPoolMaxConnecting, defaults (cherry picked from commit f75fb8f5eee2b91599334681ab2b1ebcf20b491c) |
| Comment by Githook User [ 15/Jun/17 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: A new connection pool option which controls that rate at which we add available in mongos via ShardingTaskExecutorPoolMaxConnecting, defaults (cherry picked from commit f75fb8f5eee2b91599334681ab2b1ebcf20b491c) |
| Comment by Githook User [ 02/Jun/17 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: A new connection pool option which controls that rate at which we add available in mongos via ShardingTaskExecutorPoolMaxConnecting, defaults |