[DOCS-12362] overcommit_memory kernel parameter is not documented in our production notes Created: 15/Jan/19 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Miguel Angel Nieto | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 2 |
| Labels: | docs-administration | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 0.1 |
| Description |
DescriptionHello, MongoDB shows a warning if /proc/sys/vm/overcommit_memory is set to 2, recommending to configure it to 0 or 1. See this link. In our production notes we don't mention that parameter and why we recommend that. I think we should document it to avoid customers from misconfiguring it. Once this is documented, we can reference it in our support tools. Regards, Scope of changesModify production notes (possibly the MongoDB on Linux section ) to note the recommendation for this option. |
| 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! |