[SERVER-29429] Pick a sane default for maxConnecting in sharding task executor Created: 02/Jun/17  Updated: 30/Oct/23  Resolved: 09/Aug/17

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

Type: Improvement Priority: Major - P3
Reporter: Mira Carey Assignee: Andrew Morrow (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29237 Add maxConnecting in asio connpool Closed
Documented
is documented by DOCS-10667 Docs for SERVER-29429: Pick a sane de... Closed
Duplicate
is duplicated by SERVER-28672 ASIO connection pool rate limiting Closed
Backwards Compatibility: Fully Compatible
Sprint: Platforms 2017-08-21
Participants:

 Description   

The current default is unlimited, but we may want to pick a default number for 3.6.

Something based on the number of sharding task executors, to generate no more than N (<50) simultaneously connecting connections.

The actual change is easy, but some thought should go into picking something sensible.



 Comments   
Comment by Githook User [ 09/Aug/17 ]

Author:

{'name': 'Andrew Morrow', 'username': 'acmorrow', 'email': 'acm@mongodb.com'}

Message: SERVER-29429 Pick a small but reasonable default for max pending connections
Branch: master
https://github.com/mongodb/mongo/commit/99c6768bf6931114657e108bd9f3ea96e3577c10

Comment by Daniel Pasette (Inactive) [ 02/Jun/17 ]

I'd prefer to have the default fairly low, as the usual case is that many shards (>50 shards in a cluster) all try to open conns at once and tip over a newly promoted primary on a shard.

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