# ElasticSearch pod restart very slowly

**URL:** <https://discuss.elastic.co/t/elasticsearch-pod-restart-very-slowly/231993>\
**Category:** Elasticsearch\
**Created:** [May 11, 2020, 11:19am UTC](https://discuss.elastic.co/t/elasticsearch-pod-restart-very-slowly/231993 "2020-05-11T11:19:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shyhong](https://avatars.discourse-cdn.com/v4/letter/s/59ef9b/32.png) [@shyhong](https://discuss.elastic.co/u/shyhong)\
**Post date:** [May 11, 2020, 11:19am UTC](https://discuss.elastic.co/t/elasticsearch-pod-restart-very-slowly/231993/1 "2020-05-11T11:19:28Z")

</div>

Hi all, recently I encountered a restart issue of Elasticsearch. I have a cluster with 3 nodes, last time I changed some configurations and the pod get restarted, however the pod state took almost 5 hours to become `1/1`.  
ElasticSearch version is 7.3.0, the primary shard is 50, active shards is 100 and 3 data nodes  
I used `kubectl describe po <podName>`, it only had readiness probe failed warning, like

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/5/3502842db3db020f7482cb1c3ffb40b027bdb342.png)

I used `kubectl logs <podname>`, but no log returned.

What else can I do to check what happen during the pod restart.

---

<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 8, 2020, 11:20am UTC](https://discuss.elastic.co/t/elasticsearch-pod-restart-very-slowly/231993/2 "2020-06-08T11:20:12Z")

</div>

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