[DOCS-1191] Clarify soft/hard ulimit settings, especially for "Max Processes" Created: 04/Mar/13  Updated: 26/Sep/13  Resolved: 18/Sep/13

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

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

Issue Links:
Duplicate
is duplicated by DOCS-1231 Expand on ulimit documentation Closed
Related
Participants:
Days since reply: 10 years, 22 weeks ago

 Description   

Having an insufficient soft limit on max processes can cause 'can't create new thread, closing connection' warnings/errors if the number of connections grows too high. Clarifying the difference, as it applies to MongoDB, could be helpful if the user feels the hard limit is more than sufficient.



 Comments   
Comment by auto [ 19/Sep/13 ]

Author:

{u'username': u'schmalliso', u'name': u'schmalliso', u'email': u'allison.moore@10gen.com'}

Message: DOCS-1191: clarify difference between soft and hard ulimits

Signed-off-by: Sam Kleinman <samk@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/d9257f304029518be0aded227631c2e2df95c7d1

Comment by Stephen Lee [ 27/Jun/13 ]

It might be worth mentioning in the documentation that RHEL sometimes defaults the max processes soft ulimit setting to 1024. See http://scott.cm/max-processes-1024-limits-conf/. This is a really common cause.

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