[SERVER-69299] Shard Merge to enforce backupCursorCheckpointTimestamp to be superior or equal to the startMigrationDonorTimestamp Created: 31/Aug/22  Updated: 29/Oct/23  Resolved: 15/Sep/22

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

Type: Bug Priority: Major - P3
Reporter: Mathis Bessa Assignee: Mathis Bessa
Resolution: Fixed Votes: 0
Labels: shard-merge-milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Server Serverless 2022-09-05, Server Serverless 2022-09-19
Participants:
Linked BF Score: 35

 Description   

We need an extra step in the tenant migration recipient service, for the shard merge protocol, to enforce that the backup cursor checkpoint (backupCursorCheckpointTimestamp) is superior or equal to theĀ  startMigrationDonorTimestamp.



 Comments   
Comment by Githook User [ 14/Sep/22 ]

Author:

{'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}

Message: SERVER-69299 Shard Merge to enforce backupCursorCheckpointTimestamp
Branch: master
https://github.com/mongodb/mongo/commit/d1da149077ea312efc80f8836bc79f2b1b10c1ad

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