Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-49073

Track maxConns exempt connections

XMLWordPrintableJSON

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • Service Arch 2020-08-24, Service arch 2020-09-07, Service arch 2020-10-05, Service arch 2020-11-02, Service arch 2020-11-16, Service arch 2020-11-30, Service arch 2020-12-14
    • 47

      We provide maxConns exemptions by CIDR block here. Unfortunately, our current implementation depends on one thread for one connection, determined when we start using the connection. We should mark in the session if a connection is a potential maxConns exemption. We should also track in a counter how many connections are potentially maxConns exempt. We can then rephrase the logic so that new connections are either compared against the loosened limit or the normal maxConns.

            Assignee:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: