# Getting hit by oom-killer, recommended settings?

**URL:** <https://discuss.elastic.co/t/getting-hit-by-oom-killer-recommended-settings/13631>\
**Category:** Elasticsearch\
**Created:** [September 16, 2013, 9:26pm UTC](https://discuss.elastic.co/t/getting-hit-by-oom-killer-recommended-settings/13631 "2013-09-16T21:26:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeremy\_Jongsma\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeremy_jongsma_2/32/2098_2.png) [@Jeremy\_Jongsma\_2](https://discuss.elastic.co/u/Jeremy_Jongsma_2)\
**Post date:** [September 16, 2013, 9:26pm UTC](https://discuss.elastic.co/t/getting-hit-by-oom-killer-recommended-settings/13631/1 "2013-09-16T21:26:57Z")

</div>

I'm running an ES cluster on AWS m1.large instances (7.5 GB RAM) using  
elasticsearch-servicewrapper, and am periodically getting hit by the kernel  
OOM killer.

In my configuration I have:

index.store.type: memory  
cache.memory.direct: true

My JVM memory settings are:

ES\_HEAP\_SIZE=1024  
ES\_DIRECT\_SIZE=5120m

I am currently running a 5-node cluster with 5 shards and 1 replica. The  
total index size is 3.6GB (2.7m documents). I don't ever see any java.lang.OutOfMemoryError:  
Direct buffer memory messages I've seen others report, which would seem to  
indicate to me that Java is still within its expected memory limits, but  
the kernel disagrees.

Do my settings sound reasonable for the machine size I am running on? It  
seems to me like it would be, but instances keep getting killed. Any  
direction would be appreciated.

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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:** [September 16, 2013, 10:57pm UTC](https://discuss.elastic.co/t/getting-hit-by-oom-killer-recommended-settings/13631/2 "2013-09-16T22:57:30Z")

</div>

Lower ES\_DIRECT\_SIZE and monitor if the kernel OOM killer still gets you.

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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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, 2:16am UTC](https://discuss.elastic.co/t/getting-hit-by-oom-killer-recommended-settings/13631/3 "2017-07-06T02:16:10Z")

</div>


