Shard Merge to enforce backupCursorCheckpointTimestamp to be superior or equal to the startMigrationDonorTimestamp

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Server Serverless 2022-09-05, Server Serverless 2022-09-19
    • 35
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We need an extra step in the tenant migration recipient service, for the shard merge protocol, to enforce that the backup cursor checkpoint (backupCursorCheckpointTimestamp) is superior or equal to the  startMigrationDonorTimestamp.

            Assignee:
            Mathis Bessa (Inactive)
            Reporter:
            Mathis Bessa (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: