Should the recommended value for ulimit be updated in our documentation - to reflect the new connection count limit due to SERVER-55068 (cut in half with this change)

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • ALL
    • N&O 2025-06-22, N&O 2026-07-06
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With https://jira.mongodb.org/browse/SERVER-55068, customers who previously relied on max connection count for mongodb to be calculated as ".8 * the open file limit" now have their max connection count cut to half due to the new limit being "80% of half the open file limit." 

      Our documentation still specifies ulimit recommended value to be 64000. Should the recommended new value be doubled to 128000 to allow the same number of max connection limit that the users previously had? or atleast have a note mentioning this as the "recommended solution" if customers had been impacted by this change.

       

            Assignee:
            Didier Nadeau
            Reporter:
            Manpreet Khaira
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: