[SERVER-18187] Chunk counld not split when the chunksize greater than specified chunksize Created: 23/Apr/15  Updated: 14/Apr/16  Resolved: 23/Apr/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.0.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: lsc Assignee: Unassigned
Resolution: Done Votes: 0
Labels: Bug, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: Linux
Participants:

 Description   

Here is the situation:
There is a chunk, has the shard key range [10001, 100030), but currently, it has only one key (e.g. 10001) has the data, key range from [10002, 10030) is just empty, the chuck data is beyond 8M, then we set the current chuck size to 8M.
After we fill the data in the key range(10002, 10030), this chunk starts to split, and stopped at a key range like this [10001, 10003), it has two keys, and we just wonder if this is OK or not. From the document on the official site we thought that the chunk might NOT contains more than ONE key.
So, would you please help us make sure if this is ok or not ?
What we want to is to split the chunks as many as possible, so that to make sure the data is balanced.



 Comments   
Comment by lsc [ 24/Apr/15 ]

I know this , but I think this is a bug for mongodb .Because when the real chunksize greater than specified , and the chunk contain two shard key . I don't know why the chunk counld not split , and the official document said that "In some cases, chunks can grow beyond the specified chunk size (page 662) but cannot undergo a split; e.g. if a chunk
represents a single shard key value."

Comment by Ramon Fernandez Marina [ 23/Apr/15 ]

Thanks for your report lsc. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group.

Regards,
Ramón.

Generated at Thu Feb 08 03:46:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.