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

WiredTiger instances become unresponsive due to ~120 Connections

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Performance, WiredTiger
    • Labels:
    • Environment:
      Windows Server 2012 R2, 7GB RAM
    • Windows

      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.

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

            Assignee:
            ramon.fernandez@mongodb.com Ramon Fernandez Marina
            Reporter:
            roger.dawson@ga-digital.com Roger Dawson
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: