[SERVER-68964] Reset lastCommittedOpTime to blockTimestamp after applying recipient config Created: 18/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:
Related
related to SERVER-67247 Cleanly split recipient nodes from do... Closed
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-09-05
Participants:
Linked BF Score: 15

 Description   

When a shard split recipient applies the recipient config locally, it should also reset the lastCommittedOpTime to the blockTimestamp. We will need to get the blockTimestamp from somewhere, current ideas are:

  • Query the TenantMigrationAccessBlockerRegistry for shard split access blockers (they can gain an accessor for their blockTimestamp)
  • Query the shardSplitDonors namespace for any documents representing an active shard split, and read the value directly from the state document


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

Author:

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

Message: SERVER-68964 Reset lastCommitted to blockTimestamp after split
Branch: master
https://github.com/mongodb/mongo/commit/cb38f4cfafa311b6897cd2f36b64101fcd020e5c

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