# ElasticSearch Out of Memory

**URL:** <https://discuss.elastic.co/t/elasticsearch-out-of-memory/6641>\
**Category:** Elasticsearch\
**Created:** [February 8, 2012, 5:12pm UTC](https://discuss.elastic.co/t/elasticsearch-out-of-memory/6641 "2012-02-08T17:12:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manish\_Pandit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manish_pandit/32/3000_2.png) [@Manish\_Pandit](https://discuss.elastic.co/u/Manish_Pandit)\
**Post date:** [February 8, 2012, 5:12pm UTC](https://discuss.elastic.co/t/elasticsearch-out-of-memory/6641/1 "2012-02-08T17:12:50Z")

</div>

Hi there,

We are running Elastic with 4 nodes in production. Recently we added a  
new index (~13G including the replica) and interestingly a rouge query  
failed to parse. As a result, after a few hours we are seeing the  
nodes run out of memory. The logs are full of parse exceptions. While  
we fix the query, I was curious if the excessive parse failures and/or  
logging leading to some sort of a memory leak? The nodes when bounced  
start fine and stay fine for a good number of hours, and then all of a  
sudden they run out of memory. Asking as I had an experience with this  
behavior with Tomcat back in the days, when excessive logging ended up  
creating too many references to strings which were never GCd causing  
it to go OOM.

Any input is appreciated!

-cheers,  
Manish

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [February 9, 2012, 8:12am UTC](https://discuss.elastic.co/t/elasticsearch-out-of-memory/6641/2 "2012-02-09T08:12:15Z")

</div>

No, in theory, failed queries should not cause OOM. Do you have the heap dump available?

On Wednesday, February 8, 2012 at 7:12 PM, Manish Pandit wrote:

> Hi there,
> 
> We are running Elastic with 4 nodes in production. Recently we added a  
> new index (~13G including the replica) and interestingly a rouge query  
> failed to parse. As a result, after a few hours we are seeing the  
> nodes run out of memory. The logs are full of parse exceptions. While  
> we fix the query, I was curious if the excessive parse failures and/or  
> logging leading to some sort of a memory leak? The nodes when bounced  
> start fine and stay fine for a good number of hours, and then all of a  
> sudden they run out of memory. Asking as I had an experience with this  
> behavior with Tomcat back in the days, when excessive logging ended up  
> creating too many references to strings which were never GCd causing  
> it to go OOM.
> 
> Any input is appreciated!
> 
> -cheers,  
> Manish

---

<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, 3:40am UTC](https://discuss.elastic.co/t/elasticsearch-out-of-memory/6641/3 "2017-07-06T03:40:00Z")

</div>

Closed on July 6, 2017, 3:40am UTC