[SERVER-20522] Ability to change the number of non-system connection limits at runtime Created: 21/Sep/15 Updated: 02/Dec/20 Resolved: 17/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Anil Kumar | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Service Arch 2019-11-18, Service Arch 2019-12-02, Service Arch 2019-12-16, Service Arch 2019-12-30 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
The server should have the ability to change the number of max connections at runtime using a parameter. This is specifically for controlling the number of non-system (internal / __system) connections at runtime. Although the upper limit is still controlled by the ulimits, this would enable the DBA / Admin to control the number of active connections at runtime. This will specifically be useful while performing an online controlled maintenance operation. |
| Comments |
| Comment by Benjamin Caimano (Inactive) [ 17/Dec/19 ] |
|
We do not think we are able to spend the development effort required to support this feature. As always, please feel free to reopen this ticket or submit a new ticket. |
| Comment by Anil Kumar [ 21/Sep/15 ] |
|
In case the connection are higher than the limit, user should have ability to downsize with the functionality requested in ( |
| Comment by Eric Milkie [ 21/Sep/15 ] |
|
What would be the behavior if the admin lowers the connection limit below the current number of active connections? Would everyone be locked out of the database until enough connections ended? |