[SERVER-69197] Recipient clears lastCommittedOpTime and currentCommittedSnapshot after applying recipient config Created: 26/Aug/22  Updated: 29/Oct/23  Resolved: 08/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Matt Broadstone Assignee: Matt Broadstone
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-09-05
Participants:
Linked BF Score: 165

 Description   

We originally decided to set the lastCommittedOpTime to blockOpTime when applying the recipient config, but later realized that it would be possible for that value to be different (and more important earlier) than the currentCommittedSnapshot (which is a fact propagated through WiredTiger). There is no precedent for these values moving backwards, but there is precedent for clearing these values since that simulates the environment during startup recovery, and in certain reconfig scenarios. Instead, we will clear both values when applying the recipient config.



 Comments   
Comment by Githook User [ 29/Aug/22 ]

Author:

{'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}

Message: SERVER-69197 Clear lastCommitted and currentCommitted on split
Branch: master
https://github.com/mongodb/mongo/commit/382f12ccb49dac4ac5435b35543521f96e003207

Generated at Thu Feb 08 06:12:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.