Make tenant migration recipient to start cloning tenant data only after the donor node's lastCommittedOpTime is >= startMigrationDonorTimestamp

XMLWordPrintableJSON

    • Fully Compatible
    • Repl 2021-02-22
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As part of this ticket, we need to do 2 things
      1) Tenant migration recipient should persist the startMigrationDonorTimestamp by writing it to the tenant migration recipient instance's state document.
      2) TenantMigrationRecipientService::Instance::_getStartOpTimesFromDonor() will send find commands with afterClusterTimestamp set as startMigrationDonorTimestamp and with readConcern:kMajority. That will make sure that the majority reads (for collection cloning and oplog fetching) by the recipient on the donor will be made only after startMigrationDonorTimestamp.

              Assignee:
              Matthew Russotto
              Reporter:
              Suganthi Mani
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: