after upgrade to 2.0.0 mongo starts consuming all cpu resources locking the system, complains of memory leak

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.0.1, 2.1.0
    • Affects Version/s: 2.0.0
    • Component/s: Concurrency
    • Environment:
      centos 5.6 x64
    • Linux
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      as never before, mongo started consuming full 4 cores of cpu resulting in system locking for minutes

      also complains:

      Tue Sep 13 03:09:50 [conn16410] warning: virtual size (40690MB) - mapped size (34768MB) is large. could indicate a memory leak
      Tue Sep 13 03:09:55 [conn16410] warning: virtual size (39779MB) - mapped size (34768MB) is large. could indicate a memory leak

            Assignee:
            Eliot Horowitz (Inactive)
            Reporter:
            ttt
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: