[DOCS-14119] Investigate changes in SERVER-49073: Track maxConns exempt connections Created: 13/Jan/21 Updated: 13/Nov/23 Resolved: 28/Jan/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Jason Price |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 1 week, 6 days ago | ||||||||
| Epic Link: | DOCSP-9747 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
DescriptionDownstream Change Summary In serverStatus, there are now two additional fields:
Description of Linked TicketWe 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. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 28/Jan/21 ] |
|
Author: {'name': 'Jason Price', 'email': 'jason.price@mongodb.com', 'username': 'jason-price-mongodb'}Message: |