[SERVER-18852] cannot find range (min,max) after presplit Created: 06/Jun/15  Updated: 11/Jun/15  Resolved: 11/Jun/15

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

Type: Question Priority: Major - P3
Reporter: usbuild Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

we are running mongo cluster with 5 shards, after several month of production, we find it didn't split chunks in proper ranges, some chunks never contain data while others are very heavy. so we decided to apply pre-split on one of online database. as the range of shard key is fixed, so we choose 4 moderate points as middle point. we didn't stop balancer when doing pre-split. and we think this is some what easy and non fatal.
but when we start writing to these empty and pre-splitted collections, the were still trying to autosplit, and we got "cannot find range min to max" error message. this may lead to slow insert performance and last about 8 hours. after the message "time to load chunks ", these collections start to auto split successfully. and we lost some data because of slow insert.

so, I want to know are there some essential step did i miss after pre-split? or when does "time to load chunks" happens?



 Comments   
Comment by Ramon Fernandez Marina [ 06/Jun/15 ]

Thanks for your report usbuild. 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:48:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.