[SERVER-33600] Rollback cannot set oplogTruncateAfterPoint until recoverToStableTimestamp succeeds Created: 01/Mar/18  Updated: 29/Oct/23  Resolved: 14/Mar/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: rollback-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

If it sets it, and then recoverToStableTimestamp fails due to not having a stable timestamp, then we will not have a stable checkpoint, and will truncate the oplog without having reverted the data on replication recovery.



 Comments   
Comment by Githook User [ 14/Mar/18 ]

Author:

{'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}

Message: SERVER-33600 Rollback cannot set oplogTruncateAfterPoint until recoverToStableTimestamp succeeds
Branch: master
https://github.com/mongodb/mongo/commit/2edfc326d51ba09ff83b0305155a006b39eea609

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