[SERVER-82068] Investigate handling of MinKey and MaxKey in moveChunkParallel helper Created: 11/Oct/23 Updated: 26/Oct/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
As described in this comment, it seems that there is an issue with the moveChunkParallel helper where, if one of the bounds specified includes either MinKey or MaxKey, the formatting of this key changes while creating the parallel shell, causing the migration to fail. This ticket is to either investigate why this is happening and fix it or to update these helpers to use the parallel shell helpers instead. |