[DOCS-11651] Operations checklist: Update vm.max_map_count for Linux Created: 24/Apr/18 Updated: 30/Oct/23 Resolved: 31/Oct/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrey Brindeyev | Assignee: | Emet Ozar |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||
| Description |
|
The vm.max_map_count is currently recommended to be set to 128000. mongod process will run out maps when the connection count will be high, resulting in mongod process termination. Requesting to increase at least to the 135000 to allow mongod process to handle maximum number of network connections (65536 by default in 3.2). |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Oleg Pudeyev (Inactive) [ 01/Apr/20 ] |
|
I can investigate this some more, I have some ideas. |
| Comment by Andrey Brindeyev [ 18/Feb/20 ] |
|
sue.kerschbaumer LGTM, please proceed with the change |