[SERVER-2271] Increase initial sharding limit to 256gb Created: 22/Dec/10 Updated: 12/Jul/16 Resolved: 20/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 1.8.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
There's an arbitrary limit on the size of a pre-existing collection that we're split into chunks. Alberto tells me this limit should be revisited, could possibly be removed altogether. Mostly just creating this issue to allow watchers to track progress. |
| Comments |
| Comment by Asya Kamsky [ 19/Mar/13 ] |
|
The code shows 512GB limit for 64MB default chunk size (max split points 8192) but the docs say 256GB still, opened |
| Comment by Kristina Chodorow (Inactive) [ 06/Nov/12 ] |
|
Just the data size. |
| Comment by Colin Howe [ 06/Nov/12 ] |
|
Is this a limit on the data size or the combined data/index size? |
| Comment by Eliot Horowitz (Inactive) [ 21/Feb/11 ] |
|
@andrew, its on this page: http://www.mongodb.org/display/DOCS/Sharding+Limits |
| Comment by Andrew Armstrong [ 21/Feb/11 ] |
|
I noticed on http://www.mongodb.org/display/DOCS/Sharding+FAQ that there is no mention of the limits to being able to go from an unsharded->sharded collection. Having read the docs a while ago I would have thought I was safe being unsharded until my data size grew too big; but if there is a limit to where I can transition to a sharded collection that may be worth noting in the docs? Cheers |
| Comment by Eliot Horowitz (Inactive) [ 20/Feb/11 ] |
|
Note, one way around the limit is increasing chunk size temporarily. |
| Comment by auto [ 18/Feb/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina Chodorow', u'email': u'kristina@10gen.com'}Message: increase number of initial chunk splits allowed to fit 256GB of data |
| Comment by Eliot Horowitz (Inactive) [ 18/Feb/11 ] |
|
Try making it 16x larger, and spin up a collection with 200gb, the shard and see what happens. |
| Comment by Kristina Chodorow (Inactive) [ 18/Feb/11 ] |
|
The constant should be upped for 1.8.0. It's ridiculously low (you can't chunk a collection larger than 16GBs) and shardCollection will look through the entire index regardless, which is a huge waste of resources. |