# Strategy for rolling restart with ECK?

**URL:** <https://discuss.elastic.co/t/strategy-for-rolling-restart-with-eck/374576>\
**Category:** Elasticsearch\
**Created:** [February 14, 2025, 7:29pm UTC](https://discuss.elastic.co/t/strategy-for-rolling-restart-with-eck/374576 "2025-02-14T19:29:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![blunckr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/blunckr/32/94438_2.png) [@blunckr](https://discuss.elastic.co/u/blunckr)\
**Post date:** [February 14, 2025, 7:29pm UTC](https://discuss.elastic.co/t/strategy-for-rolling-restart-with-eck/374576/1 "2025-02-14T19:29:48Z")

</div>

Hello, I'm wondering what the proper strategy is for performing rolling restarts when running Elasticsearch in K8S with ECK?

Before we ran in k8s, we followed this guide: [Full-cluster restart and rolling restart | Elasticsearch Guide [8.17] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/restart-cluster.html#restart-cluster-rolling)

After switching to ECK, I was under the impression (maybe mistakenly) that this was no longer necessary. I thought that doing a 'rollout restart' on the stateful set(s) would cause the operator do that for you? Or change some other transient settings to help with a quicker restart?

We've had some very long restarts, typically because shards start to move around once a node comes back up.

I found this guide on github: [Better Documentation for Performing Manual Rolling Restarts (of underlying hosts) of Persistent Clusters · Issue #5305 · elastic/cloud-on-k8s · GitHub](https://github.com/elastic/cloud-on-k8s/issues/5305). But I don't know if it's overkill.

I'm running version 2.3 of the operator, so I realize I could be missing newer features. I plan to update soon. But either way, I would love to see some documentation on how you are supposed to perform rolling restarts in ECK.

Thank you!