[SERVER-9365] mongod always split at 250000 position Created: 17/Apr/13 Updated: 11/Jul/16 Resolved: 23/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | 2.4.6, 2.5.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | peanutgyz | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 3 |
| 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 |
|
use mongod store small values , average size is 80 bytes, when add new shard into cluster, moveChunk start, and always say chunk is too large, can't move, then split the chunk with force:true option. mongod log: 634775618 seems to large! it is half of the collection objects count. i found in source code , s/d_split.cpp
when force is true, it will set maxChunkSize to the chunk size. but i think dataSize is the size of whole collection , not the chunk, so when force is true, it will always split at 250000 pos, not at 1/2 of the chunk. am i wrong ? |
| Comments |
| Comment by auto [ 02/Aug/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Additional test fixes. |
| Comment by auto [ 22/Jul/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Additional test fixes. |
| Comment by auto [ 20/Jul/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Revert " This reverts commit 77ab6a325498a7dd8f4a60e4c7cf1c6385f1ad98. |
| Comment by Johan Hedin [ 19/Jul/13 ] |
|
Thanks for the feedback Greg! I'm running a patch myself that's identical to your fix so I'm temporary fine. Good to see a proper solution though. |
| Comment by Greg Studer [ 19/Jul/13 ] |
|
@johan - fix is slated for backport, not yet clear when it will get to 2.4 |
| Comment by auto [ 19/Jul/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by Johan Hedin [ 18/Jun/13 ] |
|
Will the fix for this be in 2.4.5? |
| Comment by Johan Hedin [ 29/Apr/13 ] |
|
This seem to be related as well: https://groups.google.com/d/topic/mongodb-user/nJG8WlCdta0/discussion |
| Comment by Johan Hedin [ 29/Apr/13 ] |
|
This seem to bee the same problem as https://jira.mongodb.org/browse/SERVER-9498 |