[SERVER-16475] can't move chunk Created: 09/Dec/14 Updated: 24/Jan/15 Resolved: 17/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kay Agahd | Assignee: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
We are running 7 shards, each consisting of 3 replicaset members. We do pre-splitting. One of the shards is not accepting new chunks anymore, even if the chunk is empty. What can we do to get this shard accepting new chunks again?
This is the replication status of the replSet:
|
| Comments |
| Comment by Randolph Tan [ 17/Dec/14 ] | |||||||||||||||||||||||||||||||
|
You're welcome. I am closing this ticket as a duplicate. | |||||||||||||||||||||||||||||||
| Comment by Kay Agahd [ 17/Dec/14 ] | |||||||||||||||||||||||||||||||
|
Thanks so much renctan! An upgrade from 2.6.4 to 2.6.6 of the concerned shard fixed the problem. Moving chunks is possible again | |||||||||||||||||||||||||||||||
| Comment by Randolph Tan [ 16/Dec/14 ] | |||||||||||||||||||||||||||||||
|
After looking through the logs, I believe that you are running into | |||||||||||||||||||||||||||||||
| Comment by Kay Agahd [ 16/Dec/14 ] | |||||||||||||||||||||||||||||||
|
Is there anybody who could help? | |||||||||||||||||||||||||||||||
| Comment by Kay Agahd [ 11/Dec/14 ] | |||||||||||||||||||||||||||||||
|
renctan please tell me if you need supplementary info in order to sort out the issue. Since the shard is not accepting new chunks, our cluster will become unbalanced soon. Thanks for your help. | |||||||||||||||||||||||||||||||
| Comment by Kay Agahd [ 10/Dec/14 ] | |||||||||||||||||||||||||||||||
|
Randolph, here comes the error message of the moveChunk command (which took 10 hours btw.):
| |||||||||||||||||||||||||||||||
| Comment by Kay Agahd [ 09/Dec/14 ] | |||||||||||||||||||||||||||||||
|
Randolph, yes, the cluster ist using auth. The moveChunk command took so much time that I've killed it almost always. If I remember well, it failed by throwing a socket exception or cursor-not-found-exception. I'll execute it again so I can you tell you better. | |||||||||||||||||||||||||||||||
| Comment by Randolph Tan [ 09/Dec/14 ] | |||||||||||||||||||||||||||||||
|
Follow-up question: are you using auth? Is it possible to upload the logs for the primary and secondaries? Thanks! | |||||||||||||||||||||||||||||||
| Comment by Randolph Tan [ 09/Dec/14 ] | |||||||||||||||||||||||||||||||
|
Hi, If you try to use the moveChunk command manually, what kind of error message does it say? Thanks! |