-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl F (01/29/16)
-
0
Due to a race with the rollback code and applier code it is possible for a rollback to trigger OutOfOrder oplog entries because the lastAppliedOptime is not correctly reset.
- related to
-
SERVER-22132 Check in logOp that we don't record out of order oplog entries
- Closed
-
SERVER-23003 Recovery problems after network partition.
- Closed
-
SERVER-24752 Oplog as Buffer: OplogBufferCollection should save sentinel documents outside of collection
- Closed