-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.2.1
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl E (01/08/16)
-
0
This error message is a bit mislead as well. The error is due to trying to re-apply the last/current oplog entry again.
[rsSync] Fatal assertion 34361 OplogOutOfOrder Attempted to apply an earlier oplog entry (ts: Dec 18 01:16:07:1) when our lastWrittenOptime was (term: 2, timestamp: Dec 18 01:16:07:1)
After looking a bit more into this, I have found this sequence which caused the problem:
- Chained replication
- Failover with rollback
- Chained replica starts rollback while still apply with buffered oplog entries
Under these conditions it is race where this error occurs when the rollback happens during/before all the buffered oplog entries are applied.
- is duplicated by
-
SERVER-20466 Rollback and batch apply can each set minvalid independantly
- Closed
-
SERVER-21979 MongoD instance came down
- Closed
-
SERVER-22482 Cache growing to 100% followed by crash
- Closed
-
SERVER-23525 Mongo Replica Set unusable after Primary crashes with out of Memory, followed by Op Log out of Order on replica members
- Closed
- related to
-
SERVER-25145 During rollback (or w/minvalid invalid) select sync source based on end OpTime
- Closed