-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
*Location*: https://docs.mongodb.org/manual/reference/limits/#Sharding-Existing-Collection-Data-Size
*User-Agent*: Mozilla/5.0 (iPhone; CPU iPhone OS 9_2_1 like Mac OS X) AppleWebKit/601.1 (KHTML, like Gecko) CriOS/48.0.2564.104 Mobile/13D15 Safari/601.1.46
*Screen Resolution*: 375 x 667
*repo*: docs
*source*: reference/limits
*Location*: https://docs.mongodb.org/manual/reference/limits/#Sharding-Existing-Collection-Data-Size *User-Agent*: Mozilla/5.0 (iPhone; CPU iPhone OS 9_2_1 like Mac OS X) AppleWebKit/601.1 (KHTML, like Gecko) CriOS/48.0.2564.104 Mobile/13D15 Safari/601.1.46 *Screen Resolution*: 375 x 667 *repo*: docs *source*: reference/limits
Clarification needs to be made that the size of collection that can be sharded is a function of the size of the shard key (and chunk size).
Also, if we list two chunks sizes in that table, I would recommend 64MB and a larger chunk size (as 1MB is only relevant to our internal testing, and we would never recommend such a tiny chunk size and it's the wrong direction to go to shard a new collection that's large).