[SERVER-12288] Option to limit connections per database Created: 08/Jan/14  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: features we're not sure of

Type: New Feature Priority: Major - P3
Reporter: Andre de Frere Assignee: Backlog - Security Team
Resolution: Unresolved Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Server Security
Participants:
Case:

 Description   

New option similar to maxConns, that enables a user to tune the number of connections to any database.

Requirement would be to have this to be able to be tuned for specific databases, and allow the connection limit be changed dynamically.

In multi tenant situations, it would be very helpful and useful to be able to limit connections to any particular database, as this gives finer grained control than limiting the total number of connections to a host.



 Comments   
Comment by Eric Milkie [ 08/Jan/14 ]

One thing we might consider is to limit the number of authenticated sessions per user per server instance. Then you could use user permissions to achieve the goal of sessions per database.

Comment by Eliot Horowitz (Inactive) [ 08/Jan/14 ]

Connections aren't associated with a database, so not sure this is possible.

Generated at Thu Feb 08 03:28:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.