[DOCS-3613] Warn around altering maxIncomingConnections in sharded clusters Created: 18/Jun/14  Updated: 30/Oct/23  Resolved: 03/Apr/15

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: David Hows Assignee: Andrew Aldridge
Resolution: Done Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

http://docs.mongodb.org/manual/reference/configuration-options/#net.maxIncomingConnections


Participants:
Days since reply: 8 years, 45 weeks, 5 days ago

 Description   

We allow the setting of maxIncomingConnections. This can be useful in a number of circumstances but can also have a negative impact on a sharded cluster when set too low.

If your MongoS goes to make additional connections to a MongoD which has already reached its cap you will get errors.



 Comments   
Comment by Githook User [ 03/Apr/15 ]

Author:

{u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}

Message: DOCS-3613: Warn around altering maxIncomingConnections
Branch: master
https://github.com/mongodb/docs/commit/c5253ebb35c674a37eb84a281a3f466ace428cc3

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