Compute missing bound of `moveRange` within MigrationSourceManager

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.0-rc3, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v6.0
    • Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When moveRange is only invoked with one bound, the missing bound is currently computed outside the MigrationSourceManager before running a refresh. Purpose of this ticket is to optimize the current logic by moving the bound calculation after the onShardVersionMismatch to be sure that the routing table is not stale.

              Assignee:
              Pierlauro Sciarelli
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: