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

Document connPoolMaxConnsPerHost and connPoolMaxShardedConnsPerHost

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v1.3.3
    • Component/s: manual
    • Last comment by Customer:
      true
    • Actual Time:
      8

      Description

      cc: Greg Studer
      Both of these settings use the setParameter framework and are only settable at startup. Available starting in 2.6.0-rc3.

      • connPoolMaxShardedConnsPerHost - defaults to 200
        This is used for client read/write operations and represents the maximum number of connections held in the connection pool on mongos. The only reason to change this setting is if the total number of connections created is growing at the same rate as your client operations, this indicates connection churn and that this number should be raised for more efficient connection utilization.
      • connPoolMaxConnsPerHost - defaults to 200
        This is used for cluster-internal connections between shards and the config servers and authentication. It would be unusual to need to adjust this setting unless your driver is not pooling connections and you're using authentication, which would require reauthenticating every connection.

      Note, these settings do not prevent more connections from being created as needed, but the pools will not retain connections over this number.

        Attachments

          Activity

            People

            Assignee:
            sam.kleinman Sam Kleinman (Inactive)
            Reporter:
            pasette Daniel Pasette
            Participants:
            Last commenter:
            Jonathan Dahl Jonathan Dahl
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              7 years, 30 weeks, 5 days ago
              Date of 1st Reply: