-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: Server
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/reference/ulimit/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: reference/ulimit
*Location*: http://docs.mongodb.org/manual/reference/ulimit/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: reference/ulimit
-
0.5
In the SUSE ulimit note we should cover starting the server manually, which andrew.davidson@10gen.com just discovered also doesn't include the package's ulimit settings.
Maybe instead of:
The SLES packages for MongoDB adjust these limits in the default scripts, but you will need to make this change manually if you are using custom scripts and/or the tarball release rather than the SLES packages.
We could say this or something similar:
The SLES packages for MongoDB adjust these limits in the default init script, but you will need to make this change manually if you are using custom scripts, if you've installed via the tarball release rather than the SLES packages, or if you start mongod manually without using the init script.
- is related to
-
-
- Closed
-
- related to
-
SERVER-17493 Warn on startup when virtual memory limit is capped
-
- Backlog
-