# Question about out of memory **URL:** \ **Category:** Elasticsearch\ **Created:** [February 10, 2014, 2:15pm UTC](https://discuss.elastic.co/t/question-about-out-of-memory/15696 "2014-02-10T14:15:04Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![kimjmin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimjmin/32/15223_2.png) [@kimjmin](https://discuss.elastic.co/u/kimjmin)\ **Post date:** [February 10, 2014, 2:15pm UTC](https://discuss.elastic.co/t/question-about-out-of-memory/15696/1 "2014-02-10T14:15:04Z")
I'm handling about 300,000,000 log datas with elasticsearch and kibana. Using AWS instance with 8GB memory, and set es memory as -Xms4g -Xmx4g It often appears with OutOfMemory error. (java heap memory) If I use elasticsearch with Hadoop HDFS, like pre- map reducer, will it help with memory control? I didn't try yet, just want to know if it is worth to try. Thank you. -- 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/1504d530-9b78-41aa-8280-b5c9bdb04b92%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1504d530-9b78-41aa-8280-b5c9bdb04b92%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Binh\_Ly](https://avatars.discourse-cdn.com/v4/letter/b/ce7236/32.png) [@Binh\_Ly](https://discuss.elastic.co/u/Binh_Ly)\ **Post date:** [February 10, 2014, 2:36pm UTC](https://discuss.elastic.co/t/question-about-out-of-memory/15696/2 "2014-02-10T14:36:58Z")
In general, faceting, filtering, sorting, and some scripting can consume a lot of memory. Kibana usually does a lot of term and histogram facets, as well as sorting. It is likely that you'll need an instance with more memory, or if not, you need to distribute the indexes/shards around to more instances to reduce the memory requirements per instance/node. -- 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/74898b73-4b02-4d2e-8095-84d73af3bb1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/74898b73-4b02-4d2e-8095-84d73af3bb1e%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![kimjmin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimjmin/32/15223_2.png) [@kimjmin](https://discuss.elastic.co/u/kimjmin)\ **Post date:** [February 11, 2014, 4:36am UTC](https://discuss.elastic.co/t/question-about-out-of-memory/15696/3 "2014-02-11T04:36:14Z")
I changed elasticsearch.yml - index.number\_of\_shards: 10\* does it help to increase shards ? As I understand about ES Architecture is a shard means a Lucien Thread. For now, I'm more worring about memory than performance and speed. 2014년 2월 10일 월요일 오후 11시 36분 58초 UTC+9, Binh Ly 님의 말: > In general, faceting, filtering, sorting, and some scripting can consume a > lot of memory. Kibana usually does a lot of term and histogram facets, as > well as sorting. It is likely that you'll need an instance with more > memory, or if not, you need to distribute the indexes/shards around to more > instances to reduce the memory requirements per instance/node. -- 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/77f1146d-f43b-4562-84f6-e892b27f91d0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/77f1146d-f43b-4562-84f6-e892b27f91d0%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [February 11, 2014, 8:12am UTC](https://discuss.elastic.co/t/question-about-out-of-memory/15696/4 "2014-02-11T08:12:08Z")
Add more nodes. Jörg -- 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/CAKdsXoEw%3D5w4Dg7NjVOE7K9YTOa3qMVSh0G8v\_hRdp0NTXcy%2Bw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEw%3D5w4Dg7NjVOE7K9YTOa3qMVSh0G8v_hRdp0NTXcy%2Bw%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:51am UTC](https://discuss.elastic.co/t/question-about-out-of-memory/15696/5 "2017-07-06T01:51:10Z")
Closed on July 6, 2017, 1:51am UTC