[SERVER-29966] Add invariant that lastOpApplied doesn't change during secondary batch application Created: 03/Jul/17  Updated: 30/Oct/23  Resolved: 14/Feb/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.5, 3.7.3

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Kyle Suarez
Resolution: Fixed Votes: 0
Labels: rollback-non-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Repl 2018-01-15, Repl 2018-02-26
Participants:

 Description   

At the end of applying a batch we move the lastOpApplied forward - right before we do that we should invariant that the lastOpApplied is still the same as what it was at the beginning of the batch, to ensure we're never setting inconsistent points as a stable timestamp candidate.



 Comments   
Comment by Githook User [ 16/Apr/18 ]

Author:

{'name': 'Kyle Suarez', 'email': 'kyle.suarez@mongodb.com', 'username': 'ksuarz'}

Message: SERVER-29966 ensure lastOpApplied doesn't change during secondary batch application

(cherry picked from commit f7c7eae48b4656ba5df0b6c6a5662fec22899d4b)

Conflicts:
src/mongo/db/repl/sync_tail.cpp
Branch: v3.6
https://github.com/mongodb/mongo/commit/67fa9a2ea9a83ec454a4a33b42d6b762483aadbb

Comment by Githook User [ 14/Feb/18 ]

Author:

{'email': 'kyle.suarez@mongodb.com', 'name': 'Kyle Suarez', 'username': 'ksuarz'}

Message: SERVER-29966 ensure lastOpApplied doesn't change during secondary batch application
Branch: master
https://github.com/mongodb/mongo/commit/f7c7eae48b4656ba5df0b6c6a5662fec22899d4b

Generated at Thu Feb 08 04:22:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.