[SERVER-22130] Reset applier lastAppliedOptime after rollback Created: 11/Jan/16  Updated: 02/Mar/17  Resolved: 19/Jan/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.2.5, 3.3.1

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-22132 Check in logOp that we don't record o... Closed
related to SERVER-23003 Recovery problems after network parti... Closed
related to SERVER-24752 Oplog as Buffer: OplogBufferCollectio... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl F (01/29/16)
Participants:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Githook User [ 11/Mar/16 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-22130: Reset applier lastAppliedOptime after rollback

(cherry picked from commit e01916e4ef6e682f899c012d4de6282b7229168b)
Branch: v3.2
https://github.com/mongodb/mongo/commit/6970fa3ab420f7ad0e5ca30af62d5d212715d2af

Comment by Githook User [ 19/Jan/16 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-22130: Reset applier lastAppliedOptime after rollback
Branch: master
https://github.com/mongodb/mongo/commit/e01916e4ef6e682f899c012d4de6282b7229168b

Generated at Thu Feb 08 03:59:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.