[SERVER-35072] Make MigrationDestinationManager decoration on the CollectionShardingState Created: 18/May/18 Updated: 07/Dec/22 Resolved: 07/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Sprint: | Sharding 2018-06-04, Sharding 2018-06-18, Sharding 2018-07-16, Sharding 2018-07-30 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The MigrationDestinationManager should become decoration on the CollectionShardingState just like the MigrationSourceManager. Installing it on the CSS should require exclusive collection lock. |
| Comments |
| Comment by Kaloian Manassiev [ 21/Aug/18 ] |
|
It is still in CR, because we discovered race conditions. This is not critical and I am expecting blake.oler to finish it just because it got started and we spent time on it, but otherwise nothing depends on it so I am removing it from any sprints. |
| Comment by Gregory McKeon (Inactive) [ 21/Aug/18 ] |
|
kaloian.manassiev what's the status of this? |