# Shard allocation for large amount of data **URL:** \ **Category:** Elasticsearch\ **Created:** [June 9, 2014, 11:12pm UTC](https://discuss.elastic.co/t/shard-allocation-for-large-amount-of-data/18001 "2014-06-09T23:12:08Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Chen\_Wang](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@Chen\_Wang](https://discuss.elastic.co/u/Chen_Wang)\ **Post date:** [June 9, 2014, 11:12pm UTC](https://discuss.elastic.co/t/shard-allocation-for-large-amount-of-data/18001/1 "2014-06-09T23:12:08Z")
We have huge amount of data (5Billion records, 3TB in size) organized in parent / child type in one index to enable the joins. My first question is, how should I allocate shards for this big index in order to make the parent/child query more efficient? Right now doing queries will cause out of memory on several nodes, and I have 7 VMs, with 64GMem, and 1T disk. Each Es has 32Gmem allocated to it. The index has 20 shards. Any insights are helpful! Thanks, Chen -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CACim9RkMgWAxAZnLagKjnZd\_saoQdP0Gof7t0-MsK97d4F--yw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACim9RkMgWAxAZnLagKjnZd_saoQdP0Gof7t0-MsK97d4F--yw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 9, 2014, 11:23pm UTC](https://discuss.elastic.co/t/shard-allocation-for-large-amount-of-data/18001/2 "2014-06-09T23:23:02Z")
You need to add more nodes. Changing shard layout is unlikely to help if you're getting OOM. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 10 June 2014 09:12, Chen Wang [chen.apache.solr@gmail.com](mailto:chen.apache.solr@gmail.com) wrote: > We have huge amount of data (5Billion records, 3TB in size) organized in > parent / child type in one index to enable the joins. My first question is, > how should I allocate shards for this big index in order to make the > parent/child query more efficient? Right now doing queries will cause out > of memory on several nodes, and I have 7 VMs, with 64GMem, and 1T disk. > Each Es has 32Gmem allocated to it. The index has 20 shards. > > Any insights are helpful! > Thanks, > Chen > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CACim9RkMgWAxAZnLagKjnZd\_saoQdP0Gof7t0-MsK97d4F--yw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACim9RkMgWAxAZnLagKjnZd_saoQdP0Gof7t0-MsK97d4F--yw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CACim9RkMgWAxAZnLagKjnZd\_saoQdP0Gof7t0-MsK97d4F--yw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CACim9RkMgWAxAZnLagKjnZd_saoQdP0Gof7t0-MsK97d4F--yw%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624aMtfA3JVMskrPJEGOcr55%3DL2VjRteJH2pR-BTGL%3DsJRQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624aMtfA3JVMskrPJEGOcr55%3DL2VjRteJH2pR-BTGL%3DsJRQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:23am UTC](https://discuss.elastic.co/t/shard-allocation-for-large-amount-of-data/18001/3 "2017-07-06T01:23:41Z")