[SERVER-64817] Compute missing bound of `moveRange` within MigrationSourceManager Created: 23/Mar/22 Updated: 29/Oct/23 Resolved: 25/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc3, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v6.0
|
||||
| Sprint: | Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02 | ||||
| Participants: | |||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 27/Apr/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 25/Apr/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |