[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: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Platforms 2018-08-27 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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: (cherry picked from commit 8bc7ae4a94777acce2b4fc225cca5becee763a4b) |
| Comment by Githook User [ 15/Oct/18 ] |
|
Author: {'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}Message: (cherry picked from commit 1fb52e97b33c6c4ed7855994aeb7c4c4a7e64b1d) |
| Comment by Githook User [ 15/Oct/18 ] |
|
Author: {'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}Message: (cherry picked from commit 8bc7ae4a94777acce2b4fc225cca5becee763a4b) |
| Comment by Githook User [ 15/Oct/18 ] |
|
Author: {'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}Message: (cherry picked from commit 1fb52e97b33c6c4ed7855994aeb7c4c4a7e64b1d) |
| Comment by Githook User [ 21/Aug/18 ] |
|
Author: {'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}Message: |
| Comment by Githook User [ 21/Aug/18 ] |
|
Author: {'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}Message: |
| Comment by Githook User [ 16/Aug/18 ] |
|
Author: {'name': 'Siyuan Zhou', 'email': 'siyuan.zhou@mongodb.com', 'username': 'visualzhou'}Message: Revert " This reverts commit 1a643ba65b070c167cdfdd5056c7d2ac79dd5371. |
| Comment by Githook User [ 16/Aug/18 ] |
|
Author: {'username': 'jbreams', 'email': 'jbreams@mongodb.com', 'name': 'Jonathan Reams'}Message: |
| Comment by Andy Schwerin [ 15/May/18 ] |
|
To make this effective, we could consider combining it with |