[SERVER-24270] "chunk too big to move" and "chunk not full enough to trigger auto-split" Created: 24/May/16 Updated: 25/May/16 Resolved: 25/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.5, 3.2.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | xihui he | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When I tried to convert a huge collection (about 0.4 billion records) to a sharding collection, I found it could not move the chunks and could not split the chunks. When the balance tried to move the chunk, I got the following error:
When it tried to split the chunk, I got the following error:
I use default chunk size 64MB.
It seems that it fails to move because the record count is > 250001, and fails to split because the chunk size is not large enough? My mongodbs version are 3.2.5 and 3.2.6. |
| Comments |
| Comment by Ramon Fernandez Marina [ 25/May/16 ] |
|
Thanks for the update bydsky. I'm going to close this ticket as a duplicate of Regards, |
| Comment by xihui he [ 25/May/16 ] |
|
ramon.fernandez We use wiredTiger. I think the issue is exactly the same as |
| Comment by Ramon Fernandez Marina [ 24/May/16 ] |
|
bydsky, please take a look at One quick question though: which storage engine are you using? WiredTiger or MMAPv1? Thanks, |