Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-51382

[causal consistency] Ensure tenant migration donor bumps the recipient's logical clock to at least blockTimestamp

    • Minor Change
    • Sharding 2020-11-16, Sharding 2020-12-28, Sharding 2021-01-11, Sharding 2021-01-25, Sharding 2021-02-08
    • 0

      Before the recipient in a tenant migration can return success for a recipientSyncData command that includes a returnAfterReachingDonorTimestamp (set to the blockTimestamp by the tenant migration donor), it must guarantee its logical clock has durably advanced to at least that timestamp (i.e. written an oplog entry with a timestamp >= returnAfterReachingDonorTimestamp). This guarantee should apply across failovers.

            Assignee:
            jason.zhang@mongodb.com Jason Zhang (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: