[SERVER-30462] Coordinate connection and WT session limits Created: 01/Aug/17 Updated: 08/Jan/24 Resolved: 24/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| Description |
|
Currently
Each connection will require a WT session to do anything useful. So this means that if the maximum number of connections is < 20000 we fail gracefully when this number is exceeded, whereas if the maximum number of connections is > 20000 we may abort when we exceed 20000 connections. We should either make maximum number of sessions track maximum number of connections, or hard code the maximum number of connections as well. |
| Comments |
| Comment by Mira Carey [ 24/May/19 ] |
|
Closing this out, assuming that |
| Comment by Mira Carey [ 08/Apr/19 ] |
|
bruce.lucas - pinging this ticket with an update: After |
| Comment by Mira Carey [ 15/Mar/19 ] |
|
bruce.lucas mentioned
But after looking through I'd like storage to reconsider in light of that change. Additionally, I think we're overthinking a bit in terms of sizing the default limit. If we're actually 1:1 wt sessions and ingress connections / db clients, picking a slightly higher limit (up above 32768), is almost certain to be enough (as we burn a process per client, and I don't think I've seen a user in the wild which changes pid_max) Opened |