Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
*Location*: http://docs.mongodb.org/manual/reference/limits/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.122 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/search/?query=512GB
*Screen Resolution*: 1680 x 1050
*repo*: docs
*source*: reference/limits
*Location*: http://docs.mongodb.org/manual/reference/limits/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.122 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/search/?query=512GB *Screen Resolution*: 1680 x 1050 *repo*: docs *source*: reference/limits
Description
http://docs.mongodb.org/manual/reference/limits/#Sharding-Existing-Collection-Data-Size
In limits we have a strange table which discusses possible value of shard key 1003 - the limit for shard key size is 512 so we should not be using an invalid shard key size in this example table.