# 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:** 1\ **Showing post:** 5
**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. --- _[View the full topic](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)._