# Heapdump - out of memory java heap space

**URL:** <https://discuss.elastic.co/t/heapdump-out-of-memory-java-heap-space/130416>\
**Category:** Elasticsearch\
**Created:** [May 3, 2018, 9:46am UTC](https://discuss.elastic.co/t/heapdump-out-of-memory-java-heap-space/130416 "2018-05-03T09:46:52Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 6, 2018, 7:47am UTC](https://discuss.elastic.co/t/heapdump-out-of-memory-java-heap-space/130416/21 "2018-05-06T07:47:55Z")

</div>

I'd directly go to version 6.x. Specifically if you are using daily indices, start a fresh new cluster with version 6.x and let the old cluster die once you have removed all old indices.

---

<div class="post-metadata">

**Author:** ![TaskDead](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/taskdead/32/30736_2.png) [@TaskDead](https://discuss.elastic.co/u/TaskDead)\
**Post date:** [May 6, 2018, 8:11am UTC](https://discuss.elastic.co/t/heapdump-out-of-memory-java-heap-space/130416/22 "2018-05-06T08:11:15Z")

</div>

Ok, I will keep that in mind as well.

---

<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:** [June 3, 2018, 8:11am UTC](https://discuss.elastic.co/t/heapdump-out-of-memory-java-heap-space/130416/23 "2018-06-03T08:11:26Z")

</div>

Closed on June 3, 2018, 8:11am UTC

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

[Previous page](https://discuss.elastic.co/t/heapdump-out-of-memory-java-heap-space/130416.md?page=1)