-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/tutorial/choose-a-shard-key/#sharding-shard-key-cardinality
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/tutorial/choose-a-shard-key/
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: tutorial/choose-a-shard-key
*Location*: http://docs.mongodb.org/manual/tutorial/choose-a-shard-key/#sharding-shard-key-cardinality *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/tutorial/choose-a-shard-key/ *Screen Resolution*: 1440 x 900 *repo*: docs *source*: tutorial/choose-a-shard-key
Thanks for the great documentation.
We believe it's missing a very important fact about large chunks, which could be cause by incorrect selection of a shard key. Unsplittable large chunks will not be moved by the balancer. Thus, making them static to the shard they've been created on and never be able to move them, in case there's a need for it.
In "Scaling MongoDB" Kristina Chodorow writes "If a chunk gets too big, MongoDB will refuse to move it". This comment is spot on and should be in the official documentation as it affects the shard key decision.