# Restarting all data nodes

**URL:** <https://discuss.elastic.co/t/restarting-all-data-nodes/235590>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [June 3, 2020, 3:25pm UTC](https://discuss.elastic.co/t/restarting-all-data-nodes/235590 "2020-06-03T15:25:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![barracuda-charles](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@barracuda-charles](https://discuss.elastic.co/u/barracuda-charles)\
**Post date:** [June 3, 2020, 3:25pm UTC](https://discuss.elastic.co/t/restarting-all-data-nodes/235590/1 "2020-06-03T15:25:03Z")

</div>

I currently have a cluster that has dedicated data nodes that use PVC for storage. I am testing various configurations and as it stands now when I make a change using the manifest, the controller will take down each node one-by-one, keeping the cluster in a yellow / green state. However, due to the high number of nodes (and data stored within) this will take up to a day.

I'm curious if I can make the configuration change and then simply delete each of the data pods explicitly, accepting the fact that the cluster will enter a `red` state temporarily but eventually come back up and re-sync. This will be a much faster operation overall as the nodes can each come back up in parallel, accepting the fact that the state will go red until it is resync'd.

---

<div class="post-metadata">

**Author:** ![Anya\_Sabo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anya_sabo/32/49903_2.png) [@Anya\_Sabo](https://discuss.elastic.co/u/Anya_Sabo)\
**Post date:** [June 3, 2020, 5:54pm UTC](https://discuss.elastic.co/t/restarting-all-data-nodes/235590/2 "2020-06-03T17:54:16Z")

</div>

You can increase the `maxUnavailable` setting to tune this behavior: [https://www.elastic.co/guide/en/cloud-on-k8s/1.1/k8s-update-strategy.html](https://www.elastic.co/guide/en/cloud-on-k8s/1.1/k8s-update-strategy.html)

Though manually killing pods will also work, it is not the first lever I would reach for.

---

<div class="post-metadata">

**Author:** ![barracuda-charles](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@barracuda-charles](https://discuss.elastic.co/u/barracuda-charles)\
**Post date:** [June 4, 2020, 1:16am UTC](https://discuss.elastic.co/t/restarting-all-data-nodes/235590/3 "2020-06-04T01:16:30Z")

</div>

Great -- thanks for the link / info!

---

<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:** [November 4, 2022, 8:00am UTC](https://discuss.elastic.co/t/restarting-all-data-nodes/235590/4 "2022-11-04T08:00:57Z")

</div>


