[SERVER-65084] Ensure backup cursor is opened at time > startMigrationDonorTimestamp Created: 30/Mar/22  Updated: 29/Oct/23  Resolved: 15/Apr/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc1

Type: Bug Priority: Major - P3
Reporter: Christopher Caplinger Assignee: Christopher Caplinger
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
Operating System: ALL
Participants:
Linked BF Score: 14

 Description   

otherwise, the donor backup cursor opened on the recipient side may fetch and apply entries that contain index build operations before startMigrationDonorTimestamp

Options:

  • Approach 1: After the donor persists the doc with startMigrationDonorTimestamp and majority waits (basically before sending the recipientSyncData cmd), donor can trigger a stable checkpoint. This way, we can make sure when R opens a backup cursor on D, the backup cursor checkpoint timestamp is >= startMigrationDonorTimestamp.
  • Approach 2: The Recipient can retry opening the backup cursor on D until the backup cursor checkpoint ts is >= startMigrationDonorTimestamp


 Comments   
Comment by Githook User [ 15/Apr/22 ]

Author:

{'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}

Message: SERVER-65084: Ensure backup cursor is opened at time > startMigrationDonorTimestamp
Branch: master
https://github.com/mongodb/mongo/commit/53acc5a13647baaa038b8ec54b70bdf1cc17a4f8

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