# Elasticsearch Query Latency Issue During StatefulSet Rollout Restarts on ECK

**URL:** <https://discuss.elastic.co/t/elasticsearch-query-latency-issue-during-statefulset-rollout-restarts-on-eck/366462>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [September 12, 2024, 9:49am UTC](https://discuss.elastic.co/t/elasticsearch-query-latency-issue-during-statefulset-rollout-restarts-on-eck/366462 "2024-09-12T09:49:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ellie.shin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ellie.shin/32/137550_2.png) [@ellie.shin](https://discuss.elastic.co/u/ellie.shin)\
**Post date:** [September 12, 2024, 9:49am UTC](https://discuss.elastic.co/t/elasticsearch-query-latency-issue-during-statefulset-rollout-restarts-on-eck/366462/1 "2024-09-12T09:49:44Z")

</div>

Hello,

I am currently operating an Elasticsearch cluster using ECK on Kubernetes. We handle more than 1000 TPS requests to our Elasticsearch cluster. The issue we are facing is that when we apply changes like version upgrades or configuration updates to the ECK data nodes, the StatefulSet performing a rollout restart causes the shards to go into an initializing state. Even after the nodes come back up, they start without any cache, causing the query latency, which was previously within 100ms, to spike to up to 10s for the p99.

Could the Elasticsearch team please recommend a way to mitigate this issue?

Thank you.

---

<div class="post-metadata">

**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\
**Post date:** [September 13, 2024, 9:54am UTC](https://discuss.elastic.co/t/elasticsearch-query-latency-issue-during-statefulset-rollout-restarts-on-eck/366462/2 "2024-09-13T09:54:15Z")

</div>

From #Elasticsearch to #Elastic Cloud on Kubernetes (ECK)