[SERVER-4590] moveChunk aborted but still trying on shard Created: 31/Dec/11 Updated: 15/Aug/12 Resolved: 20/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
changelog shows moveChunk aborted, but db.currentOp() shows an active moveChunk for those same ranges. The logs go from showing progress on that migration to suddenly logs from a moveChunk with all the data is empty/zeroes. See linked CS ticket comments from Dec 30 for more info. |