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

Wiredtiger very high CPU usage

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.11
    • Component/s: WiredTiger
    • Labels:
      None
    • Environment:
      Debian 7, xeon d1521, 32gb ram, 2x480gb ssd, 1gbit networking

      I'm running a 3 member replicaset. The average workload is very constant and does not push load average above 2-3. When workload increases (for example due to a delay in our processing queue) mongodb starts processing queries very fast but after about 5-10 minutes completely starts hogging userspace CPU usage (100%, load average 120-130).

      Even when completely shutting down the workload, load average still stays at 120-130, the only way for it to go back to normal is running rs.stepDown() and force another member to be primary. This instance then (usually) starts processing the requests very fast but sometimes still goes back to the very high load average.

      In the mongodb log I can see write requests are taking a very long time (some upto 10 seconds).

      I'm not really sure how to prevent this as it completely disables my whole workload.

        1. Screen Shot 2017-01-06 at 11.59.28.png
          Screen Shot 2017-01-06 at 11.59.28.png
          416 kB
        2. Screen Shot 2017-01-09 at 13.15.39.png
          Screen Shot 2017-01-09 at 13.15.39.png
          165 kB
        3. Screen Shot 2017-01-09 at 13.15.49.png
          Screen Shot 2017-01-09 at 13.15.49.png
          194 kB
        4. Screen Shot 2017-01-09 at 13.44.14.png
          Screen Shot 2017-01-09 at 13.44.14.png
          71 kB

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            vincentvm Vincent van Megen
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: