ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In this report derived from the linked HELP ticket, we see linear growth of ConnectionPool::SpecificPool over time. We'd like to know why this is happening.

      The report was generated from shard 00-02, on the mongos.

      In order of priority:

      1. Is this a leak related to SERVER-135020? My initial judgement says no, but it's possible.
      2. Do we need to change any log verbosity components on the server to find out more? We need to know this ASAP if so.
      3. Why is this memory growing, is it a leak or is it legitimate usage that will grow over the lifetime of a process?

            Assignee:
            Michael Nugent
            Reporter:
            Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: