[DOCS-6865] Add a note about /etc/systemd/system/mongodprod.service.d/limits.conf for systemd Created: 22/Dec/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

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

Type: Improvement Priority: Minor - P4
Reporter: James O'Leary Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Distros using Systemd


Issue Links:
Related
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

We should also mention that with systemd you can update /etc/systemd/system/mongodprod.service.d/limits.conf on the following note on the https://docs.mongodb.org/manual/reference/ulimit/#unix-ulimit-settings page:

NOTE
Red Hat Enterprise Linux and CentOS 6 place a max process limitation of 1024 which overrides ulimit settings. Create a file named /etc/security/limits.d/99-mongodb-nproc.conf with new soft nproc and hard nproc values to increase the process limit. See /etc/security/limits.d/90-nproc.conf file as an example.



 Comments   
Comment by Education Bot [ 01/Nov/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 Roy Rim [ 24/Sep/16 ]

It looks like the format of the file is different? Like the contents of limits.conf would look like:

[Service]
LimitNOFILE=64000

Oh and it looks like you would have to restart the systemd daemon otherwise it won't pick it up (whut?)

http://stackoverflow.com/questions/27849331/how-to-set-nginx-max-open-files/36423859#36423859

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