# Control the \`update\` order

**URL:** <https://discuss.hashicorp.com/t/control-the-update-order/15302>\
**Category:** Nomad\
**Created:** [October 8, 2020, 3:01pm UTC](https://discuss.hashicorp.com/t/control-the-update-order/15302 "2020-10-08T15:01:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![powellchristoph](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/powellchristoph/32/12565_2.png) [@powellchristoph](https://discuss.hashicorp.com/u/powellchristoph)\
**Post date:** [October 8, 2020, 3:01pm UTC](https://discuss.hashicorp.com/t/control-the-update-order/15302/1 "2020-10-08T15:01:04Z")

</div>

Hello! I am running a service that uses leader elections. I’d love to be able to somehow save the active leader until last in the rolling update to prevent consecutive elections impacting the service. I don’t see an obvious native solution, has someone solved this without introducing a completely custom deploy?

thanks!

---

<div class="post-metadata">

**Author:** ![yw22](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/yw22/32/25035_2.png) [@yw22](https://discuss.hashicorp.com/u/yw22)\
**Post date:** [April 20, 2022, 5:25pm UTC](https://discuss.hashicorp.com/t/control-the-update-order/15302/2 "2022-04-20T17:25:09Z")

</div>

Just pop up this thread again. I have similar question. It is better to support rolling update strategy from newest to oldest OR from oldest to newest. Not sure if it is feasible or not.