[SERVER-19365] Allow one extra connection from localhost even if mongod is out of connections Created: 10/Jul/15 Updated: 06/Dec/22 Resolved: 04/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Igor Canadi | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Sprint: | Service Arch 2019-11-18, Service Arch 2019-12-02, Service Arch 2019-12-16, Service Arch 2019-12-30, Service Arch 2020-01-13 | ||||||||
| Participants: | |||||||||
| Description |
|
We had a situation where mongod ran out of connections and we couldn't connect to it with a shell. There was little we can do without a shell access. It would be good to allow one extra connection from localhost. That way we'd be able to debug and remediate mongo even in these situations. As a background, check out https://jira.mongodb.org/browse/SERVER-19360 |
| Comments |
| Comment by Mira Carey [ 04/Feb/20 ] |
|
We currently exempt unix domain sockets from maxConns checks. Given that, I'm closing this as wontfix, as using the unix domain socket is an applicable workaround. |