# Script to do a ES rolling upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [February 26, 2015, 4:11am UTC](https://discuss.elastic.co/t/script-to-do-a-es-rolling-upgrade/22399 "2015-02-26T04:11:18Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![burtonator](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/burtonator/32/44790_2.png) [@burtonator](https://discuss.elastic.co/u/burtonator)\ **Post date:** [February 26, 2015, 4:11am UTC](https://discuss.elastic.co/t/script-to-do-a-es-rolling-upgrade/22399/1 "2015-02-26T04:11:18Z")
It seems like there should be a script out there (I'm lazy) that someone has already written to do a per -node restart after an upgrade. It should block until the cluster is green again so you can move on to the next host. I was going to write something in ansible but it seems to be easier to just find a single rolling-restart script which can do it... -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/64ef396e-2994-45d7-9eca-ea0052fdd688%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/64ef396e-2994-45d7-9eca-ea0052fdd688%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:30am UTC](https://discuss.elastic.co/t/script-to-do-a-es-rolling-upgrade/22399/2 "2017-07-06T00:30:00Z")