[SERVER-49073] Track maxConns exempt connections Created: 24/Jun/20 Updated: 29/Oct/23 Resolved: 07/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Service Arch 2020-08-24, Service arch 2020-09-07, Service arch 2020-10-05, Service arch 2020-11-02, Service arch 2020-11-16, Service arch 2020-11-30, Service arch 2020-12-14 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 47 | ||||||||||||||||||||||||
| Description |
|
We provide maxConns exemptions by CIDR block here. Unfortunately, our current implementation depends on one thread for one connection, determined when we start using the connection. We should mark in the session if a connection is a potential maxConns exemption. We should also track in a counter how many connections are potentially maxConns exempt. We can then rephrase the logic so that new connections are either compared against the loosened limit or the normal maxConns. |
| Comments |
| Comment by Githook User [ 03/Dec/20 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |
| Comment by Githook User [ 14/Sep/20 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |