[SERVER-34684] --maxConns parameter limit both client and replica connections Created: 26/Apr/18 Updated: 06/Dec/22 Resolved: 09/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sergey Zagursky | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
In the case when `mongod` hits connection limit it stops accepting connection both from clients and from other replicas in its replicaset. |
| Comments |
| Comment by Sergey Zagursky [ 10/Nov/21 ] |
|
@Lauren Lewis, your link leads to |
| Comment by Lauren Lewis (Inactive) [ 09/Nov/21 ] |
|
We, the Server Team, plan to address this through a related initiative. Closing & will investigate further through the initiative. |
| Comment by Peter Ivanov [ 18/Dec/19 ] |
|
Are there any current development plans relevant to this issue? |
| Comment by Mira Carey [ 08/May/18 ] |
|
There are a few issues at play with limiting the number of connections to a mongod in a replicaset:
This is a reasonable ask, and we'll look into providing a way to ensure that cases 2 and 3 work if --maxConns is reached. |
| Comment by Sergey Zagursky [ 27/Apr/18 ] |
|
It looks like Fortnite suffered from this issue too: https://www.epicgames.com/fortnite/en-US/news/postmortem-of-service-outage-4-12 |