# Out of Memory issue

**URL:** <https://discuss.elastic.co/t/out-of-memory-issue/7553>\
**Category:** Elasticsearch\
**Created:** [May 3, 2012, 3:15pm UTC](https://discuss.elastic.co/t/out-of-memory-issue/7553 "2012-05-03T15:15:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kartavya](https://avatars.discourse-cdn.com/v4/letter/k/65b543/32.png) [@Kartavya](https://discuss.elastic.co/u/Kartavya)\
**Post date:** [May 3, 2012, 3:15pm UTC](https://discuss.elastic.co/t/out-of-memory-issue/7553/1 "2012-05-03T15:15:54Z")

</div>

Hi All,

I have around 70gb index size and 33992470 doc index.  
I am running facet queries on this index. Query are giving prompt response  
if i am using single client to query.

But the same system hang and goes out of memory when using multiple clients  
to query at the same time.

I have assigned 10g memory to the elastic search.

Can anybody guide me where is the problem and what is the resolution?

I tried flush api to recover memory but it didn't help.

Thanks in advance.

~Pulkit

---

<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:** [May 4, 2012, 1:57pm UTC](https://discuss.elastic.co/t/out-of-memory-issue/7553/2 "2012-05-04T13:57:36Z")

</div>

If multiple clients are running and causing you problem, maybe that fact  
that several search requests executing concurrently is the problem. Are you  
asking for facets that return a lot of data? Also, monitor the JVM heap  
memory usage (big desk can help here), if its really close to 10g, you need  
to either increase the memory allocate to ES, or add more nodes to the  
cluster.

On Thu, May 3, 2012 at 6:15 PM, Pulkit Agrawal [pulkitdotcom@gmail.com](mailto:pulkitdotcom@gmail.com)wrote:

> Hi All,
> 
> I have around 70gb index size and 33992470 doc index.  
> I am running facet queries on this index. Query are giving prompt response  
> if i am using single client to query.
> 
> But the same system hang and goes out of memory when using multiple  
> clients to query at the same time.
> 
> I have assigned 10g memory to the Elasticsearch.
> 
> Can anybody guide me where is the problem and what is the resolution?
> 
> I tried flush api to recover memory but it didn't help.
> 
> Thanks in advance.
> 
> ~Pulkit

---

<div class="post-metadata">

**Author:** ![Kartavya](https://avatars.discourse-cdn.com/v4/letter/k/65b543/32.png) [@Kartavya](https://discuss.elastic.co/u/Kartavya)\
**Post date:** [June 10, 2012, 4:57pm UTC](https://discuss.elastic.co/t/out-of-memory-issue/7553/3 "2012-06-10T16:57:39Z")

</div>

Hi Shay,

I try to install big desk using "plugin -install lukas-vlcek/bigdesk" but  
on running the same I got the error it will work for 0.19.x or 0.20.x.  
I am using 0.18.7 what should we do to resolve it. I want to use big desk  
to monitor my Elasticsearch Instance.

Please help.

Thanks,  
Pulkit Agrawal

On Fri, May 4, 2012 at 7:27 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:

> If multiple clients are running and causing you problem, maybe that fact  
> that several search requests executing concurrently is the problem. Are you  
> asking for facets that return a lot of data? Also, monitor the JVM heap  
> memory usage (big desk can help here), if its really close to 10g, you need  
> to either increase the memory allocate to ES, or add more nodes to the  
> cluster.
> 
> On Thu, May 3, 2012 at 6:15 PM, Pulkit Agrawal [pulkitdotcom@gmail.com](mailto:pulkitdotcom@gmail.com)wrote:
> 
> > Hi All,
> > 
> > I have around 70gb index size and 33992470 doc index.  
> > I am running facet queries on this index. Query are giving prompt  
> > response if i am using single client to query.
> > 
> > But the same system hang and goes out of memory when using multiple  
> > clients to query at the same time.
> > 
> > I have assigned 10g memory to the Elasticsearch.
> > 
> > Can anybody guide me where is the problem and what is the resolution?
> > 
> > I tried flush api to recover memory but it didn't help.
> > 
> > Thanks in advance.
> > 
> > ~Pulkit

---

<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:25am UTC](https://discuss.elastic.co/t/out-of-memory-issue/7553/4 "2017-07-06T03:25:01Z")

</div>

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