[SERVER-54666] Use earlier oplog entry if recovery timestamp cannot be found in oplog Created: 19/Feb/21  Updated: 29/Oct/23  Resolved: 09/Jun/21

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 5.0.0-rc2, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-51049 Cannot assume recovery timestamp can ... Closed
is related to SERVER-51158 Must not truncate entire oplog before... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Repl 2021-05-31, Repl 2021-06-14
Participants:
Linked BF Score: 121

 Description   

During recovery, we assume that the oplogApplicationStartPoint exists in the oplog.

The oplogApplicationStartPoint derives from the stable timestamp, which is not guaranteed to be in the oplog. If the stable timestamp was greater than the oplogTruncateAfterPoint, then we move this point back to the truncate after point, which is guaranteed to be in the oplog. However, if the stable timestamp is less than the oplogTruncateAfterPoint, we don't do anything to fix the oplogApplicationStartPoint.

Because of SERVER-51158, we guarantee that an oplog entry less than or equal to the stable timestamp exists in the oplog, so we should move the oplogApplicationStartPoint back to that oplog entry.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 12/Jun/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-54666 Use earlier oplog entry if recovery timestamp cannot be found in oplog

(cherry picked from commit 8f2183cc0f064b477e90c903701815369a867807)
Branch: v5.0
https://github.com/mongodb/mongo/commit/a7916f97f70735d889de98582b5107008953e0eb

Comment by Githook User [ 08/Jun/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-54666 Use earlier oplog entry if recovery timestamp cannot be found in oplog
Branch: master
https://github.com/mongodb/mongo/commit/8f2183cc0f064b477e90c903701815369a867807

Generated at Thu Feb 08 05:34:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.