# Is there any way to downgrade elasticsearch from 8.15 to 7.17?

**URL:** <https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856>\
**Category:** Elasticsearch\
**Created:** [December 11, 2024, 3:40pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856 "2024-12-11T15:40:11Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![debayan1](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@debayan1](https://discuss.elastic.co/u/debayan1)\
**Post date:** [December 11, 2024, 3:40pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/1 "2024-12-11T15:40:11Z")

</div>

Is there any way to downgrade elasticsearch from 8.15 to 7.17 ?  
We were using elasticsearch version 7.17.  
Now, we upgraded to elasticsearch version and using collectors in backward compatibility mode in order to communicate with elasticsearch 8.15.

---

<div class="post-metadata">

**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:** [December 11, 2024, 4:14pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/2 "2024-12-11T16:14:33Z")

</div>

Elasticsearch does not support downgradesso you would need to either restore a snapshot taken before you upgraded into a 7.17 cluster or reindex your data back into 7.17.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 11, 2024, 5:29pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/3 "2024-12-11T17:29:30Z")

</div>

What would be the reason of downgrading?

---

<div class="post-metadata">

**Author:** ![debayan1](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@debayan1](https://discuss.elastic.co/u/debayan1)\
**Post date:** [December 15, 2024, 1:43pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/4 "2024-12-15T13:43:01Z")

</div>

we are trying ways to upgrade upgrade elasticsearch in production. we have tested in test environments till now.  
if something goes wrong, then we need to revert to previous elasticsearch version

---

<div class="post-metadata">

**Author:** ![debayan1](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@debayan1](https://discuss.elastic.co/u/debayan1)\
**Post date:** [December 15, 2024, 1:44pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/5 "2024-12-15T13:44:06Z")

</div>

also, what is the approach of elasticsearch during upgrade? is it a blue green approach? is there any downtime during the upgrade of a cluster?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [December 15, 2024, 1:59pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/6 "2024-12-15T13:59:29Z")

</div>

> [@debayan1](#):
>
> if something goes wrong, then we need to revert to previous elasticsearch version

This is not possible, Elasticsearch does not support downgrade, so you need to check everything.

If something goes wrong you will need to fix it before continuing to upgrade.

> [@debayan1](#):
>
> also, what is the approach of elasticsearch during upgrade? is it a blue green approach? is there any downtime during the upgrade of a cluster?

If you will have a downtime depends on how your cluster is configured, how many nodes you have etc.

Did you read the [documentation about upgrade](https://www.elastic.co/guide/en/elastic-stack/current/upgrading-elastic-stack.html#prepare-to-upgrade)? You need to read this before trying to upgrade.

---

<div class="post-metadata">

**Author:** ![debayan1](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@debayan1](https://discuss.elastic.co/u/debayan1)\
**Post date:** [December 16, 2024, 9:21am UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/7 "2024-12-16T09:21:28Z")

</div>

ok..  
can you tell if the elasticsearch upgrade follows a blue-green approach?

---

<div class="post-metadata">

**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:** [December 16, 2024, 9:26am UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/8 "2024-12-16T09:26:18Z")

</div>

The normal way to upgrade Elasticsearch is to do an in-place rolling upgrade. You should make sure you run the upgrade assistant and test it out first in a test cluster as you can not downgrade. If you want to do blue-green that is something you will need to orchestrate and manage yourself.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [December 16, 2024, 12:15pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-downgrade-elasticsearch-from-8-15-to-7-17/371856/9 "2024-12-16T12:15:26Z")

</div>

> [@debayan1](#):
>
> can you tell if the elasticsearch upgrade follows a blue-green approach?

Did you check the documentation? It explains how the upgrade works.

You can do a rolling-upgrade where you can upgrade your nodes without having a downtime, but this is not a blue-green approach.

Once you start the upgrade you need to finish as having a cluster with nodes with different versions can lead to other issues.
