[SERVER-53552] Tenant migration donor should pass startMigrationDonorTimestamp info to recipient via recipientSyncData cmd Created: 04/Jan/21  Updated: 29/Oct/23  Resolved: 16/Feb/21

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: pm-1791_alpha, pm-1791_milestone-B
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-50495 [passthrough suite] Make tenant_migra... Closed
is depended on by SERVER-53553 Make tenant migration recipient to st... Closed
Related
is related to SERVER-48862 Donor should not be able to start/com... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2021-02-08, Repl 2021-02-22
Participants:

 Description   

startMigrationDonorTimestamp indicates that the recipient should start cloning/fetching tenant data from donor only after that timestamp. This ticket should address 2 things.

1) Add a new field "startMigrationDonorTimestamp" in recipientSyncData cmd

2) Tenant migration donor would set the startMigrationDonorTimestamp to donor lastAppliedTimestamp (which is >= donor initial state doc write timestamp)



 Comments   
Comment by Githook User [ 16/Feb/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: SERVER-53552 Tenant migration donor should pass startMigrationDonorTimestamp info to recipient via recipientSyncData cmd
Branch: master
https://github.com/mongodb/mongo/commit/7648dc6152e8f24ca626b6cd120d9d701c37bf2d

Generated at Thu Feb 08 05:31:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.