Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-2763

Describe how/ when MMS issues a "low open files limit" warning

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor - P4
    • Resolution: Done
    • None
    • v1.3.3
    • Cloud Manager
    • None
    • 4

    Description

      Describe how/ when MMS issues a "low open files limit alert" with something like this:

      On a host-by-host basis, MMS considers the number of available server connections as reported in the serverStatus.connections object embedded inside Ping documents, for example:

          "serverStatus": {
              "connections": {
                     "current": 4,
                     "totalCreated": 379514,
                     "available": 815
              }
          }

      The message "Host has low open files limit" is issued when the sum of current and available is less than minRequiredConnections, where the latter is defined like this:

      If
         "maxConns" command line parameter is set for the server
      Then
         minRequiredConnections = minimum(maxConns, 20000) - 1
      Else 
         minRequiredConnections = 1024

      The use of "ulimit" in the warning in the Ping document is potentially confusing. However, the "max open file descriptors" ulimit parameter directly affects the number of available server connections, and hence affects the above metric.

      Further, the "open files limit" parameter is related to db.hostInfo()['extra'].maxOpenFiles, which is available in the Ping documents.

      I note that while "maxOpenFiles" exists in the extra document in Linux, I do not see it in the extra document on my Mac.

      Attachments

        Activity

          People

            tim.slavin Tim Slavin
            jacob.ribnik@mongodb.com Jacob Ribnik
            Jess Mokrzecki Jess Mokrzecki
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              9 years, 33 weeks, 1 day ago