[SERVER-6231] os x - startup warning - maxproc - hard limit of 1024 Created: 28/Jun/12  Updated: 11/Jul/16  Resolved: 03/Jul/12

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.1.2
Fix Version/s: 2.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Ryan Nitz Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Darwin Rnz4c.local 11.4.0 Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64 i386


Operating System: ALL
Participants:

 Description   

This warning looks like an error. Why do you need the max processes so high?

I cannot set the maxproc on OS X above 1024.

sudo launchctl limit maxproc 1024

If, I increase, it asserts:

ulimit -u 1025
ulimit: max user processes: cannot modify limit: Operation not permitted

But this works:

ulimit -u 1024

The startup warning is:

    "startupWarnings": {
        "log": [
            "Wed Jun 27 19:02:40 [initandlisten] ",
            "Wed Jun 27 19:02:40 [initandlisten] ** NOTE: This is a development version (2.1.2) of MongoDB.",
            "Wed Jun 27 19:02:40 [initandlisten] **       Not recommended for production.",
            "Wed Jun 27 19:02:40 [initandlisten] ",
            "Wed Jun 27 19:02:40 [initandlisten] ** WARNING: soft rlimits too low. rlimits set to 1024 processes, 20000 files. Number of processes should be at least 0.5 times number of files.",
            "Wed Jun 27 19:02:40 [initandlisten] "
        ],
        "ok": 1
    },

I added this in /etc/sysctl.conf and rebooted but nada:

kern.maxprocs=2048



 Comments   
Comment by auto [ 03/Jul/12 ]

Author:

{u'date': u'2012-07-03T09:53:46-07:00', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-6231 - warnings on os x too aggresive given default kernel settings
Branch: master
https://github.com/mongodb/mongo/commit/67c3bf018684706aac870ff3fc5f82731fa72c61

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