[SERVER-16540] Potential race in migration can have an aborted migration consume MigrateStatus::_cloneLocs Created: 12/Dec/14 Updated: 06/Dec/22 Resolved: 01/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.8.0-rc2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Sharding 10 (02/19/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
There are cases where the donor shard can abort the migration without contacting the recipient shard. If it starts another migration before the recipient shard realizes it, then it can call _cloneMigrate against the donor shard and interfere with the new migration. A similar issue exist for _transferMods as well. |