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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • 1.8.2
    • 1.9.2
    • Replication, Stability
    • None
    • Ubuntu EC2 Linux on m2.4xlarge
    • ALL

    Description

      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.

      Attachments

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

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-3447 journal exception during large operations within db.eval (multi update)

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              dwight@mongodb.com Dwight Merriman
              mikeyk Mike K
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: