[SERVER-28672] ASIO connection pool rate limiting Created: 07/Apr/17  Updated: 08/Jan/24  Resolved: 09/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Samantha Ritter (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
duplicates SERVER-29429 Pick a sane default for maxConnecting... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4, v3.2
Sprint: Platforms 2017-04-17, Platforms 2017-07-31, Platforms 2017-08-21
Participants:

 Description   

There is currently no concept of rate limiting on the egress connection pool. Currently, the connection pool hands out new connections whenever they are requested, which can lead to large and immediate spikes of new connections and threads on the target server. We should add rate limiting to the connection pool to mitigate these types of bursts in traffic to avoid overwhelming hosts with new connections.



 Comments   
Comment by Andrew Morrow (Inactive) [ 09/Aug/17 ]

Per discussion with mira.carey@mongodb.com, we believe that the correct way to achieve rate limiting here is by setting a small default value for max connecting, which is the goal of SERVER-29429.

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