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

XMLWordPrintableJSON

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

      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 (Inactive)
              Reporter:
              Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: