Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
mongodb 3.2
*Location*: https://docs.mongodb.com/manual/core/sharding-introduction/
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.122 Safari/537.36 SE 2.X MetaSr 1.0
*Referrer*: https://docs.mongodb.com/?_ga=1.255109824.958390077.1461633920
*Screen Resolution*: 1366 x 768
mongodb 3.2 *Location*: https://docs.mongodb.com/manual/core/sharding-introduction/ *User-Agent*: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.122 Safari/537.36 SE 2.X MetaSr 1.0 *Referrer*: https://docs.mongodb.com/?_ga=1.255109824.958390077.1461633920 *Screen Resolution*: 1366 x 768
Description
If the mongoDB has the balancer that can migrating the chunks in shards to maintaing the data balance.why you say "range based partitioning can result in an uneven distribution of data, which may negate some of the benefits of sharding. For example, if the shard key is a linearly increasing field, such as time, then all requests for a given time range will map to the same chunk, and thus the same shard."