[SERVER-86295] Change move collection command to lazily track unsharded collection Created: 06/Feb/24 Updated: 07/Feb/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PM-3364-Milestone-4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
moveCollection uses the resharding machinery to do an online movement of user data. There is a precondition though: the collection must be tracked. The purpose of this ticket is to make moveCollection to track the collection if it's unsharded and then use the resharding machinery. This could be achieved by for example creating a _shardsvrMoveCollection command that first spawns a coordinator to track the collection, and then spawns the resharding coordinator. |