mongod complains about too much data uncommitted, crashes with assertionFailure, then fails to start

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Critical - P2
    • 1.9.2
    • Affects Version/s: 1.8.2
    • Component/s: Replication, Stability
    • None
    • Environment:
      Ubuntu EC2 Linux on m2.4xlarge
    • ALL
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The Primary of one of our replica sets suddenly died with the attached stack trace (mongocrash.log) and now refuses to start, throwing stack traces like the one in mongocrash2.log.

        1. mongocrash.log
          5 kB
        2. mongocrash2.log
          48 kB
        3. repair-crash.txt
          4 kB

            Assignee:
            Dwight Merriman
            Reporter:
            Mike K
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: