# Java heap space error - 99% after increase

**URL:** <https://discuss.elastic.co/t/java-heap-space-error-99-after-increase/122493>\
**Category:** Logstash\
**Created:** [March 5, 2018, 11:35am UTC](https://discuss.elastic.co/t/java-heap-space-error-99-after-increase/122493 "2018-03-05T11:35:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stevesimpson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stevesimpson/32/41437_2.png) [@stevesimpson](https://discuss.elastic.co/u/stevesimpson)\
**Post date:** [March 5, 2018, 11:35am UTC](https://discuss.elastic.co/t/java-heap-space-error-99-after-increase/122493/1 "2018-03-05T11:35:40Z")

</div>

Hi,

Over the weekend I saw a number of `java.lang.OutOfMemoryError: Java heap space` errors in the logstash logs. After reading the docs I've tuned the default settings up to 16G (32GB Server) however I'm are still seeing `JVM Heap: 99.80% (16GB / 16GB)` in the kibana monitoring screen.

Kibana monitoring screen attached showing cluster info, this is still very much a proof of concept at this stage so we will absolutely be looking at how we are indexing at replicating data before going live.

 ![18-03-05-11%3A33%3A20](https://us1.discourse-cdn.com/elastic/original/3X/0/2/022bafe9be3740e28589b4b19dd90b65918cbb25.png)

Is this normal behaviour for logstash, or do I have a memory leak somewhere. If this is not normal behaviour, how would I go about trying to debug this.

Many thanks

---

<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:** [April 2, 2018, 11:36am UTC](https://discuss.elastic.co/t/java-heap-space-error-99-after-increase/122493/2 "2018-04-02T11:36:17Z")

</div>

Closed on April 2, 2018, 11:36am UTC

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