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.
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: