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

MongoDB Slave Crashed During Replication

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Duplicate
    • Affects Version/s: 3.2.8
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL

      Description

      Node in replica set crashed during replication with the following error:

      2016-10-11T09:33:29.057-0400 I REPL [rsBackgroundSync] Starting rollback due to OplogStartMissing: our last op time fetched: (term: 215, timestamp: Oct 11 00:07:01:1). source's GTE: (term: 216, timestamp: Oct 11 00:07:51:1) hashes: (-3078676073172300872/7746078569620926355)
      2016-10-11T09:33:29.057-0400 I - [rsBackgroundSync] Fatal assertion 18750 UnrecoverableRollbackError: need to rollback, but in inconsistent state. minvalid: (term: 216, timestamp: Oct 11 00:07:51:1) > our last optime: (term: 215, timestamp: Oct 11 00:07:01:1)
      2016-10-11T09:33:29.057-0400 I - [rsBackgroundSync]

      ***aborting after fassert() failure

        Attachments

        1. mongod.log
          70.53 MB

          Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-7200 use oplog as op buffer on secondaries

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26415 Make sure to catch up to minValid before exiting rollback

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-25848 Enforce single sync source during rollback

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

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: