Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.2.5, 3.3.1
Affects Version/s: None
Component/s: Replication
Labels:
- code-only

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Completed:

3.2.5
Sprint:
Repl F (01/29/16)
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Scott Hernandez (Inactive)
Reporter:: Scott Hernandez (Inactive)
Participants:: Githook User, Scott Hernandez
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jan 11 2016 06:13:01 PM UTC
Updated:: Mar 02 2017 07:19:46 PM UTC
Resolved:: Jan 19 2016 04:07:53 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates