[SERVER-31688] W SHARDING [conn161595] can't accept new chunks because there are still 1 deletes from previous migration Created: 24/Oct/17 Updated: 27/Oct/23 Resolved: 25/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | vegaoqiang | Assignee: | Kaloian Manassiev |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos7.2 |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
in mongo cluster have 8 shard, As the "chunk" distribution is uneven, so i check mongos log or mongod log, found the following messages: 2017-10-24T14:36:54.135+0800 W SHARDING [conn161595] can't accept new chunks because there are still 1 deletes from previous migration so how can i found the previous migration chunk and deletes it with manually, and is there any way to solve this problem without restart a shard? |
| Comments |
| Comment by Kaloian Manassiev [ 25/Oct/17 ] | |
|
vegaoqiang, no problem. I presume your shards each are replica sets - is that correct? If so, this may potentially be related to The message in question should look something like this:
| |
| Comment by vegaoqiang [ 25/Oct/17 ] | |
|
Hi Mr. Kal, | |
| Comment by Kaloian Manassiev [ 24/Oct/17 ] | |
|
Hi vegaoqiang, The most likely reason for the outstanding deletes from a previous migration is that the orphan cleanup process is blocked behind open cursors. Finding and killing this cursor should unblock orphan cleanup. Would it be possible to attach the complete log from the same shard node? There should be a message from the [RangeDeleter] thread, which indicates the cursors on which it is blocked. Best regards, |