# Elasticsearch es-client pods are down after master node reboot

**URL:** <https://discuss.elastic.co/t/elasticsearch-es-client-pods-are-down-after-master-node-reboot/337442>\
**Category:** Elasticsearch\
**Created:** [July 3, 2023, 10:34am UTC](https://discuss.elastic.co/t/elasticsearch-es-client-pods-are-down-after-master-node-reboot/337442 "2023-07-03T10:34:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shyamsundar\_Rajkumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shyamsundar_rajkumar/32/122951_2.png) [@Shyamsundar\_Rajkumar](https://discuss.elastic.co/u/Shyamsundar_Rajkumar)\
**Post date:** [July 3, 2023, 10:34am UTC](https://discuss.elastic.co/t/elasticsearch-es-client-pods-are-down-after-master-node-reboot/337442/1 "2023-07-03T10:34:22Z")

</div>

I have deployed Elasticsearch 7 in our kubernetes cluster. The es-client-7 pods are going down when the master node is rebooted. When checking logs I found "master not discovered yet" . The statefulsets es-master and es-data were running in the master node itself and its understandable that when we reboot, this statefulsets pods are also restarted.

I tired to drain the pods in master node before reboot but still ended up in same situation even before the reboot. Is there some wrong configurations in the ES deployment and statefulsets?

NOTE: As a workaround I am scaling down all the statefulsets and deployments of ES and then scaling up to make all the pods running again.

---

<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:** [July 31, 2023, 10:34am UTC](https://discuss.elastic.co/t/elasticsearch-es-client-pods-are-down-after-master-node-reboot/337442/2 "2023-07-31T10:34:24Z")

</div>

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