-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Networking
-
None
-
Fully Compatible
-
v4.0, v3.6
-
Platforms 2018-08-27
-
(copied to CRM)
-
0
MongoDB Cloud Services always need to be able to connect to database processes in order to perform their core admin operations–gather statistics, perform backups, change configuration, perform various maintenance operations, etc.
In order to ensure that they can always connect and are not locked out by user sessions – using up all available slots under maxConns – we need a way to specify a CIDR block that is exempt from the maxConns limit. This can then be used with all mongod/mongos processes managed by MongoDB Cloud Services, ensuring that the Cloud Services can always perform their critical tasks.
- is duplicated by
-
SERVER-36285 Allow connections to override maxConns based on CIDR range
- Closed
- is related to
-
SERVER-40376 when maxIncomingConnectionsOverride contains invalid CIDR block, allows connections from any CIDR block
- Closed
-
SERVER-40377 when maxIncomingConnectionsOverride contains invalid CIDR block, allows connections from any CIDR block
- Closed
-
SERVER-1889 Support different networks / nics for client & replication traffic
- Closed
-
SERVER-2425 Create protected login for mongo for admin operations
- Closed
- related to
-
SERVER-49073 Track maxConns exempt connections
- Closed
-
SERVER-48980 Associate ServiceExecutors with Clients
- Closed