[SERVER-25985] rlimit check for nProcesses > 0.5 nFiles fails for non-trivial, valid WiredTiger configurations Created: 07/Sep/16  Updated: 21/Aug/19  Resolved: 21/Aug/19

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Bug Priority: Major - P3
Reporter: Jared D. Cottrell Assignee: Gregory Wlodarek
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-08-26
Participants:
Case:

 Description   

We're commonly running into this warning in environments we feel are properly configured. It's a warning, not an error, but it's still creating friction through confusion among the user base, so it would be nice to address.

WARNING: soft rlimits too low. rlimits set to XXX processes, YYY files. Number of processes should be at least YYY/2 : 0.5 times number of files.

The issue is that WiredTiger now uses a file descriptor per namespace, meaning the number of file descriptors required can quickly outstrip the number of connections used in heavily multi-tenanted environments (commonly development and test) where connection requirements are modest but namespaces abound.

You can see a more detailed discussion from the mongodb-user group:

https://groups.google.com/d/topic/mongodb-user/aUrWTZxUUi4/discussion



 Comments   
Comment by Githook User [ 21/Aug/19 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-25985 Remove rlimit check for nProcesses and nFiles during startup
Branch: master
https://github.com/mongodb/mongo/commit/f5ee95fe7e9e6ca3db9db01e97a917f754d4d8cd

Comment by Kelsey Schubert [ 09/Sep/16 ]

Hi jared,

Thank you for reporting this behavior - I'm marking this ticket to indicate that it needs to be scheduled. Please continue to watch for updates.

Kind regards,
Thomas

Generated at Thu Feb 08 04:10:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.