[SERVER-9945] Hard coded MaxObjectPerChunk limit Created: 17/Jun/13 Updated: 10/Dec/14 Resolved: 26/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Thomas Adam | 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 |
|
Hi, why ist the MaxObjectPerChunk hard coded in line: https://github.com/mongodb/mongo/blob/master/src/mongo/s/chunk.cpp#L54? I found that in line: https://github.com/mongodb/mongo/blob/master/src/mongo/s/d_migrate.cpp#L408 the calculated maxRecsWhenFull will be reseted to the hard coded MaxObjectPerChunk limit if its greater. Our configured chunk size is 64mb and the chunk has a size of ~32mb, so it should be moved without problems. I added to the failed response some values to validate this and here is the output:
So a chunk with over 250000 entries can't be moved? IMHO it's not expacted or? We think for that reason is our cluster not good distributed. We have many abort logs in the config.changelog. Any thoughts? Thanks & Regards |
| Comments |
| Comment by David Hows [ 26/Aug/13 ] | |||||
|
Hi Thomas, I'm marking this ticket as resolved as this is now being dealt with on your private ticket. The solution to this issue looks to be the changes being made as part of Regards, | |||||
| Comment by Johan Hedin [ 18/Jun/13 ] | |||||
|
This sounds quite related to A chunk that is "too big to move" will be "force split" but the bug reported in Same root case as in this one; small document size with respect to max chunk size. I posted some comments about this in the discussion on the mailing list https://groups.google.com/forum/?fromgroups#!topic/mongodb-user/leyazB-1zec | |||||
| Comment by Thomas Adam [ 17/Jun/13 ] | |||||
|
Ok, I have created the ticket SUPPORT-608. Thanks | |||||
| Comment by Scott Hernandez (Inactive) [ 17/Jun/13 ] | |||||
|
Yes, please create a Community Private issue (private to the submitter and support), upload the logs there and then we can link them together without exposing your private information here. | |||||
| Comment by Thomas Adam [ 17/Jun/13 ] | |||||
|
Short question. Can we make the ticket private about our intern logs? Thanks | |||||
| Comment by Thomas Adam [ 17/Jun/13 ] | |||||
|
We use 2.4.4. We use a hashed shard key of a MongoID. I run the following command:
I can split the given chunk, but this not what I want. I have splitted the chunk bevor, because of the same message and one of the new chunks (the above) has the same problem! The logs prints only the same information which the response give me. Log of mongos:
| |||||
| Comment by Scott Hernandez (Inactive) [ 17/Jun/13 ] | |||||
|
What version are you using? What is the chunk definition look like which cannot be moved? If it can be split it will try to do so if possible before moving it, did that have an error. If you upload the server logs and mongos logs for that time it would be helpful. |