[DOCS-7678] Production Checklist pid_max recommendation not consistent with Unix ulimits recommendations Created: 18/Apr/16  Updated: 30/Oct/23  Resolved: 25/Apr/16

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

Type: Bug Priority: Major - P3
Reporter: Kevin Pulo Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 7 years, 42 weeks, 2 days ago

 Description   

On the ulimits page we recommend setting nproc to 64000.

But in the Production Checklist for Linux, we recommend setting kernel.pid_max to only 32768.

This is inconsistent with the ulimits recommendations (which have been generally accepted as good baseline values, to the point that 64000 is used in the default mongod init scripts these days), because setting nproc to 64000 is useless if the system can only have less than 64000 concurrently running pids.

Therefore, the Production Checklist should be updated to recommend a kernel.pid_max value of 64000.



 Comments   
Comment by Githook User [ 25/Apr/16 ]

Author:

{u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kev@pulo.com.au'}

Message: DOCS-7678 recommend kernel.pid_max of 64000

This is to match the ulimits nproc recommendation of 64000.

Signed-off-by: kay <kay.kim@10gen.com>
Branch: v3.0
https://github.com/mongodb/docs/commit/31fccb87bd1194b58d27e908e54225c437112c06

Comment by Githook User [ 25/Apr/16 ]

Author:

{u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kev@pulo.com.au'}

Message: DOCS-7678 recommend kernel.pid_max of 64000

This is to match the ulimits nproc recommendation of 64000.

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/d9de36c1ab53bca103a2433943b65e9cb8c9d493

Comment by Kevin Pulo [ 18/Apr/16 ]

Pull request: https://github.com/mongodb/docs/pull/2603

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