[SERVER-51233] Warn on startup if vm.max_map_count < 2 * max connections Created: 30/Sep/20 Updated: 29/Oct/23 Resolved: 27/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Logging |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Sommer | Assignee: | Vojislav Stojkovic |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sa-groomed, save-for-alex, save-for-vojislav | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service Arch 2021-06-14, Service Arch 2021-06-28, Service Arch 2021-09-20, Service Arch 2021-10-04 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
In our production notes we recommend setting:
This corresponds to our default max connections of 64k, as each connection requires 2 maps. Upon startup, the mongod should check this value (/proc/sys/vm/max_map_count) and warn if it doesn't equal 2*max connections.
Acceptance Criteria: We warn users that vm.max_map_count doesn't exceed 2x max connections |
| Comments |
| Comment by Billy Donahue [ 28/Sep/21 ] |
|
code review took place here: |
| Comment by Githook User [ 27/Sep/21 ] |
|
Author: {'name': 'Vojislav Stojkovic', 'email': 'vojislav.stojkovic@mongodb.com', 'username': 'vstojkovic-mongodb'}Message: |
| Comment by Githook User [ 24/Sep/21 ] |
|
Author: {'name': 'Vojislav Stojkovic', 'email': 'vojislav.stojkovic@mongodb.com', 'username': 'vstojkovic-mongodb'}Message: |