Details
-
Bug
-
Status: Closed
-
Critical - P2
-
Resolution: Duplicate
-
3.2.8
-
None
-
None
-
None
-
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
Issue Links
- duplicates
-
SERVER-7200 use oplog as op buffer on secondaries
-
- Closed
-
- related to
-
SERVER-26415 Make sure to catch up to minValid before exiting rollback
-
- Closed
-
-
SERVER-25848 Enforce single sync source during rollback
-
- Closed
-