[SERVER-26675] Remove 3.2 shard compatibility from MigrationManager in 3.6 Created: 18/Oct/16 Updated: 06/Dec/22 Resolved: 16/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Sprint: | Sharding 2018-02-26 | ||||||||
| Participants: | |||||||||
| Description |
|
This should simplify the MigrationManager logic. There is probably some clean up that could happen on the MigrationSourceManager, as well, like the takeDistLock parameter in the shard moveChunk command. |