# Rolling upgrade/restart guide?

**URL:** <https://forum.opensearch.org/t/rolling-upgrade-restart-guide/10869>\
**Category:** DevOps\
**Created:** [September 8, 2022, 3:58pm UTC](https://forum.opensearch.org/t/rolling-upgrade-restart-guide/10869 "2022-09-08T15:58:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ericallen](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/ericallen/32/3136_2.png) [@ericallen](https://forum.opensearch.org/u/ericallen)\
**Post date:** [September 8, 2022, 3:58pm UTC](https://forum.opensearch.org/t/rolling-upgrade-restart-guide/10869/1 "2022-09-08T15:58:56Z")

</div>

What is the process for doing a rolling upgrade/restart of OpenSearch? ES has a guide like at [Rolling upgrades | Elasticsearch Guide [7.17] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/rolling-upgrades.html) . Is the ES guide still valid for OS or has there been any changes made to the process for OS?

The reason I am asking, I was following pretty close that that ES rolling upgrade guide to go from 1.3.2 to 2.2.0. After each data node was restarted, 1 or 2 shard pair (primary and replica) would go offline and need to be reinstallized. This would take the cluster red. It was alway with a current days index.