[SERVER-27880] Rate Limit Mongos Outbound Thread Creation Created: 31/Jan/17  Updated: 28/May/19  Resolved: 28/May/19

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

Type: Improvement Priority: Critical - P2
Reporter: Kevin Arhelger Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-29237 Add maxConnecting in asio connpool Closed
Related
is related to SERVER-29237 Add maxConnecting in asio connpool Closed
Participants:
Case:

 Description   

Currently, mongos can create an unlimited number of outbound connections to mongod's

In cases with many (a few hundred) mongos routers a temporary slowdown causes a massive, sudden increase in connections to the mongod's.

SERVER-25027 allows limiting the number of outbound connections, but this is a manual setting requiring manual configuration and testing to determine an optimal value.

What would be more beneficial is to implement a feedback loop between mongos and mongod, where new connections are rate limited slowing or preventing the negative performance implications from additional connections.

This would hopefully prevent needing to manually set SERVER-25027 settings and reduce the overall number of connection spikes.



 Comments   
Comment by Mira Carey [ 28/May/19 ]

This was solved inĀ SERVER-29237 through the introduction of the maxConnecting parameter in the new sharding task executor connection pool.

Generated at Thu Feb 08 04:16:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.