[SERVER-36834] chunk migration blocked on orphan cleanup Created: 24/Aug/18 Updated: 06/Dec/22 Resolved: 24/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | 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 | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
On a sharded collection with two chunks (both chunks initially on the same shard), when I tried to move one of the chunks to the other shard and back again, the second moveChunk operation that would return the chunk back to its initial location seemed to be blocked on the deferred CollectionRangeDeleter operation:
Both moveChunk commands were executed with _waitForDelete: false. |
| Comments |
| Comment by Kaloian Manassiev [ 24/Aug/18 ] |
|
This is a duplicate of SERVER-31837. For your purposes, you can just set orphanCleanupDelaySecs = 0 so you can move the chunk back immediately. |