# Whole cluster stucked instead of single node

**URL:** <https://discuss.elastic.co/t/whole-cluster-stucked-instead-of-single-node/140105>\
**Category:** Elasticsearch\
**Created:** [July 16, 2018, 8:42am UTC](https://discuss.elastic.co/t/whole-cluster-stucked-instead-of-single-node/140105 "2018-07-16T08:42:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mats990](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mats990/32/37516_2.png) [@mats990](https://discuss.elastic.co/u/mats990)\
**Post date:** [July 16, 2018, 8:42am UTC](https://discuss.elastic.co/t/whole-cluster-stucked-instead-of-single-node/140105/1 "2018-07-16T08:42:55Z")

</div>

Hi,

We are running ES 5.6.4 on Java 1.8.0\_171.  
Lately we can observe that linux process is stucked in zombie state on one VM (not always the same one). At that time, ES cluster doesn't throw any errors, doesn't process requests at all, everything is hanging and from client side we receive a lot of timeout exceptions from whole cluster. The only solution is to reboot linux OS on node where process is in zombie state. At that point cluster recovers.  
The issue seems to be on linux side but the main question here is:  
why is the whole cluster down when only one instance(only data node) has issues?

Kr

---

<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:** [August 13, 2018, 8:42am UTC](https://discuss.elastic.co/t/whole-cluster-stucked-instead-of-single-node/140105/2 "2018-08-13T08:42:55Z")

</div>

Closed on August 13, 2018, 8:42am UTC

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