# ES nodes crashing randomly since upgrade to ES5.2

**URL:** <https://discuss.elastic.co/t/es-nodes-crashing-randomly-since-upgrade-to-es5-2/80785>\
**Category:** Elasticsearch\
**Created:** [March 31, 2017, 9:02am UTC](https://discuss.elastic.co/t/es-nodes-crashing-randomly-since-upgrade-to-es5-2/80785 "2017-03-31T09:02:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![crickes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/crickes/32/18009_2.png) [@crickes](https://discuss.elastic.co/u/crickes)\
**Post date:** [March 31, 2017, 9:02am UTC](https://discuss.elastic.co/t/es-nodes-crashing-randomly-since-upgrade-to-es5-2/80785/1 "2017-03-31T09:02:36Z")

</div>

Ever since I upgrade my clusters to ES5.2, I have been plagued with random crashes of Elasticsearch. The only thing I see in the logs is this entry in the messages log, there is nothing in the elasticsearch log at the time of the crash:

elasticsearch.service: main process exited, code=killed, status=6/ABRT

I search on here and found some old threads talking about this, but there didn't appear to be any clear root cause. Some said it went away of a hardware change, others after upgrading the JVM. These nodes have been running ES2.2 for over a year with an issue and they are all running JVM 1.8.77. I haven't upgraded the JVM. Is there a bug in this JVM that has only been exposed by ES5 perhaps? I'm scratching my head a little trying to figure out how to stabilise the cluster.

---

<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 28, 2017, 9:03am UTC](https://discuss.elastic.co/t/es-nodes-crashing-randomly-since-upgrade-to-es5-2/80785/2 "2017-04-28T09:03:11Z")

</div>

Closed on April 28, 2017, 9:03am UTC

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