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

WiredTiger instances become unresponsive due to ~120 Connections

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Performance, WiredTiger
    • Labels:
    • Environment:
      Windows Server 2012 R2, 7GB RAM
    • Operating System:
      Windows

      Description

      We have a 5 node replica set, running 2 MMAP, 2 WiredTiger and 1 arbiter instance. Upon making WiredTiger a primary our web-server become unresponsive. Further investigation revealed the number of connections had gone from ~25 to 120.

      The problem appears to manifest itself when our system is on catch up and thus more heavily loaded that usual. The load is not exceptional though, with only a single threaded service performing multiple reads and writes to MongoDB, and a web-server connecting to MongoDB and performing reads for the most part with only a handful of users.

      The MMAP instances do not appear to exhibit this problem.

        Attachments

        1. currentop.json
          63 kB
          Roger Dawson
        2. mongo-wiredtigerunresponsive.log
          294 kB
          Roger Dawson

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: