# Logstash Consuming too Much JVM

**URL:** <https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860>\
**Category:** Logstash\
**Created:** [March 17, 2020, 7:39am UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860 "2020-03-17T07:39:36Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![shrikantgulia](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@shrikantgulia](https://discuss.elastic.co/u/shrikantgulia)\
**Post date:** [March 17, 2020, 7:39am UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/1 "2020-03-17T07:39:36Z")

</div>

Hello,

My Logstash is Consuming too much JVM due to it Logstash is getting shut down and not receiving any data.  
I have 4 Pipelines running in my Logstash and  
Can Some one suggest me What all steps to followed for tunning it

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/1/914ae405d66e2b218b9af9f8c6ae63799ee2ad56.png)

Thanks in Advance

---

<div class="post-metadata">

**Author:** ![shrikantgulia](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@shrikantgulia](https://discuss.elastic.co/u/shrikantgulia)\
**Post date:** [April 8, 2020, 8:13am UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/2 "2020-04-08T08:13:04Z")

</div>

Can Please someone advice me

Regards

---

<div class="post-metadata">

**Author:** ![shrikantgulia](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@shrikantgulia](https://discuss.elastic.co/u/shrikantgulia)\
**Post date:** [April 17, 2020, 1:54pm UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/3 "2020-04-17T13:54:57Z")

</div>

I am facing this issue even after increasing the JVM

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/6/86d94edb0ba25cbffe73680d43b923eefcf7c8a5.png)

Can Some one Please guide me

Regards

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 17, 2020, 3:05pm UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/4 "2020-04-17T15:05:08Z")

</div>

It's pretty obvious you have a memory leak. Ever higher heap utilization after GCs, long GC pauses once the heap fills until an OOM causes a restart. I suggest you read [this](https://discuss.elastic.co/t/java-heap-space/225496/2).

---

<div class="post-metadata">

**Author:** ![shrikantgulia](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@shrikantgulia](https://discuss.elastic.co/u/shrikantgulia)\
**Post date:** [April 18, 2020, 4:03am UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/5 "2020-04-18T04:03:47Z")

</div>

Hello @Badger,

Thank you for the response.  
How to enable heap dump  
Can You Please guide me

I am Using  
Centos Linux 7  
\*\*  
openjdk version "1.8.0\_131"  
OpenJDK Runtime Environment (build 1.8.0\_131-b12)  
OpenJDK 64-Bit Server VM (build 25.131-b12, mixed mode)  
\*\*  
and to collect JVM heap dump  
bash: jmap: command not found...  
Regards

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 18, 2020, 5:16pm UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/6 "2020-04-18T17:16:12Z")

</div>

I would try -XX:+HeapDumpOnOutOfMemoryError to see if your JVM supports that.

---

<div class="post-metadata">

**Author:** ![shrikantgulia](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@shrikantgulia](https://discuss.elastic.co/u/shrikantgulia)\
**Post date:** [April 19, 2020, 6:45am UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/7 "2020-04-19T06:45:10Z")

</div>

> [@Badger](#):
>
> -XX:+HeapDumpOnOutOfMemoryError

Hello @Badger,

Thank you for the response

![image](https://us1.discourse-cdn.com/elastic/original/3X/4/7/47075171dbe4ba290205ca7d0550b591e2d2a804.png)  
I would be thankful If You guide me to solve this issue

Regards

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 19, 2020, 3:05pm UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/8 "2020-04-19T15:05:22Z")

</div>

You should place it on the JVM command line, in jvm.options, for example.

---

<div class="post-metadata">

**Author:** ![shrikantgulia](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@shrikantgulia](https://discuss.elastic.co/u/shrikantgulia)\
**Post date:** [April 21, 2020, 5:52am UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/9 "2020-04-21T05:52:44Z")

</div>

> [@Badger](#):
>
> -XX:+HeapDumpOnOutOfMemoryError

Hello @Badger  
It has already been added

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/7/a796f828b691f385c2a11b3f221d7c0ca9eccdb4.png)

Regards

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 21, 2020, 3:38pm UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/10 "2020-04-21T15:38:32Z")

</div>

OK, so when your JVM runs out of memory it should generate a heap dump and you will need to analyze it. I suggest you keep the heap small so that the heap dump is manageable. If you JVM runs out of heap at 8 GB it will be a lot easier to work with than if it runs out at 48 GB.

---

<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:** [May 19, 2020, 3:38pm UTC](https://discuss.elastic.co/t/logstash-consuming-too-much-jvm/223860/11 "2020-05-19T15:38:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
