[DOCS-1374] Misleading statement in ulimit docs (memory limits, OOM killer) Created: 10/Apr/13  Updated: 30/Oct/23  Resolved: 22/Apr/13

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 10 years, 45 weeks ago

 Description   

The footnote at the bottom of the reference/ulimit page currently reads as follows:

If you limit the resident memory size on a system running MongoDB you risk allowing the operating system to terminate the mongod process under normal situations. Do not set this value. If the operating system (i.e. Linux) kills your mongod, with the OOM killer, check the output of serverStatus and ensure MongoDB is not leaking memory.

"If you limit the resident memory size on a system running MongoDB you risk allowing the operating system to terminate the mongod process" is misleading; when a process reaches one of its memory limits (data segment size, virtual memory size, resident page count) the operating system does not kill the process, it instead refuses to honor further allocation calls for that limit (e.g. brk/mmap/etc => ENOMEM). The sentence about the OOM killer needs to be moved to a different paragraph; it needs to be made clearer that the OOM killer is not invoked to target processes that have reached their memory limits.


Generated at Thu Feb 08 07:40:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.