# ES is upgraded from version 6.3.2 to 6.8.22 in a rolling manner. After the upgrade, the cluster status is abnormal. How to roll back to 6.3.2? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 12, 2022, 7:18am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533 "2022-05-12T07:18:22Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![qiuxb](https://avatars.discourse-cdn.com/v4/letter/q/48db29/32.png) [@qiuxb](https://discuss.elastic.co/u/qiuxb)\ **Post date:** [May 12, 2022, 7:18am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/1 "2022-05-12T07:18:22Z")
Currently I am working on the ES rolling upgrade plan. The official manual lists the rolling upgrade steps, but there is no rollback step. After the ES rolling upgrade, the cluster status is abnormal or the application wants to roll back to 6.3.2. How to do it? Rollback from ES version 6.8.22 to 6.3.2 ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 12, 2022, 7:46am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/2 "2022-05-12T07:46:27Z")
Elasticsearch does not support rollbacks, so the only way to get back to 6.3.2 would be to restore a snapshot taken with that version prior to the upgrade into a downgraded 6.3.2 cluster. It is probably better to fix the issue you are having. What is the issue with the cluster status? What is in the Elasticsearch logs? ---
**Author:** ![qiuxb](https://avatars.discourse-cdn.com/v4/letter/q/48db29/32.png) [@qiuxb](https://discuss.elastic.co/u/qiuxb)\ **Post date:** [May 12, 2022, 9:41am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/3 "2022-05-12T09:41:35Z")
Currently, I am working on a rolling upgrade plan for ES, from version 6.3.2 to 6.8.22. In order to prevent uncontrollable problems during the upgrade and cannot be solved in a short time, I hope to have a cluster upgrade rollback plan to deal with ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 12, 2022, 9:46pm UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/4 "2022-05-12T21:46:05Z")
As Christian mentioned, the only plan is to take a snapshot and restore that. ---
**Author:** ![qiuxb](https://avatars.discourse-cdn.com/v4/letter/q/48db29/32.png) [@qiuxb](https://discuss.elastic.co/u/qiuxb)\ **Post date:** [May 17, 2022, 10:11am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/5 "2022-05-17T10:11:01Z")
Thanks for the reply, I have a question about rolling upgrades, the part marked in the following text, is it understood that it is not allowed to accept multiple ES versions for a long time during the upgrade? However, the actual rolling upgrade requires a gradual upgrade of nodes one by one, and needs to wait for the node status to recover and the cluster status to recover to green, which may take a long time. During this period, two versions of ES must exist in the cluster at the same time. Rolling upgrades A rolling upgrade allows an Elasticsearch cluster to be upgraded one node at a time so upgrading does not interrupt service. **Running multiple versions of Elasticsearch in the same cluster beyond the duration of an upgrade is not supported,** as shards cannot be replicated from upgraded nodes to nodes running the older version. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 17, 2022, 10:18pm UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/6 "2022-05-17T22:18:47Z")
> [@qiuxb](#): > > a long time Yeah, as in days/weeks. A few hours is fine. ---
**Author:** ![qiuxb](https://avatars.discourse-cdn.com/v4/letter/q/48db29/32.png) [@qiuxb](https://discuss.elastic.co/u/qiuxb)\ **Post date:** [May 18, 2022, 1:08am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/7 "2022-05-18T01:08:49Z")
So is it safer to roll the upgrade in a few hours? The largest amount of ES cluster data in our production environment exceeds 20TB, so I am worried that the rolling upgrade will take a long time. Is there a precise time requirement for the rolling upgrade to complete? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 18, 2022, 1:09am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/8 "2022-05-18T01:09:35Z")
There's no hard limits here, but hours is ok. ---
**Author:** ![qiuxb](https://avatars.discourse-cdn.com/v4/letter/q/48db29/32.png) [@qiuxb](https://discuss.elastic.co/u/qiuxb)\ **Post date:** [May 18, 2022, 1:10am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/9 "2022-05-18T01:10:32Z")
ok thanks for your reply ---
**Author:** ![qiuxb](https://avatars.discourse-cdn.com/v4/letter/q/48db29/32.png) [@qiuxb](https://discuss.elastic.co/u/qiuxb)\ **Post date:** [May 18, 2022, 9:23am UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/10 "2022-05-18T09:23:58Z")
ES rolling upgrade, upgrade from version 6.3.2 to 6.8.22 and version 7.x to 7.16.2, does the client application need to make any changes? What preparations and inspections need to be done before upgrading? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 18, 2022, 9:37pm UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/11 "2022-05-18T21:37:04Z")
Most likely. You will need to read the breaking changes for the client and do testing ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 15, 2022, 9:37pm UTC](https://discuss.elastic.co/t/es-is-upgraded-from-version-6-3-2-to-6-8-22-in-a-rolling-manner-after-the-upgrade-the-cluster-status-is-abnormal-how-to-roll-back-to-6-3-2/304533/12 "2022-06-15T21:37:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.