[SERVER-34986] CIDR Block That is Exempt from maxConns Created: 14/May/18  Updated: 29/Oct/23  Resolved: 21/Aug/18

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 3.6.9, 4.0.4, 4.1.3

Type: New Feature Priority: Major - P3
Reporter: Matt Lord (Inactive) Assignee: Jonathan Reams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-11989 Docs for SERVER-34986: CIDR Block Tha... Closed
Duplicate
is duplicated by SERVER-36285 Allow connections to override maxConn... Closed
Problem/Incident
Related
related to SERVER-49073 Track maxConns exempt connections Closed
related to SERVER-48980 Associate ServiceExecutors with Clients Closed
is related to SERVER-40376 when maxIncomingConnectionsOverride c... Closed
is related to SERVER-40377 when maxIncomingConnectionsOverride c... Closed
is related to SERVER-1889 Support different networks / nics for... Closed
is related to SERVER-2425 Create protected login for mongo for ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0, v3.6
Sprint: Platforms 2018-08-27
Participants:
Case:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Githook User [ 15/Oct/18 ]

Author:

{'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}

Message: SERVER-34986 Fix unit test

(cherry picked from commit 8bc7ae4a94777acce2b4fc225cca5becee763a4b)
Branch: v3.6
https://github.com/mongodb/mongo/commit/c1693a4b0c7a54189ee9a95fc18f1b95084bfc3f

Comment by Githook User [ 15/Oct/18 ]

Author:

{'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}

Message: SERVER-34986 Allow connections to override maxConns based on CIDR range

(cherry picked from commit 1fb52e97b33c6c4ed7855994aeb7c4c4a7e64b1d)
Branch: v3.6
https://github.com/mongodb/mongo/commit/042426218620111f8f9e299f7b0da7f088b22565

Comment by Githook User [ 15/Oct/18 ]

Author:

{'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}

Message: SERVER-34986 Fix unit test

(cherry picked from commit 8bc7ae4a94777acce2b4fc225cca5becee763a4b)
Branch: v4.0
https://github.com/mongodb/mongo/commit/1110e8f75d6c22bd0318eafcf87af3e67eb24a40

Comment by Githook User [ 15/Oct/18 ]

Author:

{'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}

Message: SERVER-34986 Allow connections to override maxConns based on CIDR range

(cherry picked from commit 1fb52e97b33c6c4ed7855994aeb7c4c4a7e64b1d)
Branch: v4.0
https://github.com/mongodb/mongo/commit/e1d1ca31a74ddc43eb72bbadcc071c19f6396050

Comment by Githook User [ 21/Aug/18 ]

Author:

{'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}

Message: SERVER-34986 Fix unit test
Branch: master
https://github.com/mongodb/mongo/commit/8bc7ae4a94777acce2b4fc225cca5becee763a4b

Comment by Githook User [ 21/Aug/18 ]

Author:

{'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}

Message: SERVER-34986 Allow connections to override maxConns based on CIDR range
Branch: master
https://github.com/mongodb/mongo/commit/1fb52e97b33c6c4ed7855994aeb7c4c4a7e64b1d

Comment by Githook User [ 16/Aug/18 ]

Author:

{'name': 'Siyuan Zhou', 'email': 'siyuan.zhou@mongodb.com', 'username': 'visualzhou'}

Message: Revert "SERVER-34986 Allow connections to override maxConns based on CIDR range"

This reverts commit 1a643ba65b070c167cdfdd5056c7d2ac79dd5371.
Branch: master
https://github.com/mongodb/mongo/commit/5e461534b339c957d2e6dcf16015949a496a1110

Comment by Githook User [ 16/Aug/18 ]

Author:

{'username': 'jbreams', 'email': 'jbreams@mongodb.com', 'name': 'Jonathan Reams'}

Message: SERVER-34986 Allow connections to override maxConns based on CIDR range
Branch: master
https://github.com/mongodb/mongo/commit/1a643ba65b070c167cdfdd5056c7d2ac79dd5371

Comment by Andy Schwerin [ 15/May/18 ]

To make this effective, we could consider combining it with SERVER-1889 so that cluster members can also generally connect.

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