# Elasticsearch upgrade strategies

**URL:** <https://discuss.elastic.co/t/elasticsearch-upgrade-strategies/263706>\
**Category:** Elasticsearch\
**Created:** [February 9, 2021, 10:00am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-strategies/263706 "2021-02-09T10:00:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vangap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vangap/32/44927_2.png) [@vangap](https://discuss.elastic.co/u/vangap)\
**Post date:** [February 9, 2021, 10:00am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-strategies/263706/1 "2021-02-09T10:00:54Z")

</div>

Hi,

We have a situation where our application breaks when upgraded to a new minor version. I would like to get the community thoughts on how this can better be solved.

There are some breaking changes documented and undocumented when moving from 7.1 -\> 7.9/10  
Notably \_index, alias [change](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/release-notes-7.5.0.html#breaking-7.5.0)

Even though ES rest client is forward compatible, our application breaks in terms of its behavior when the older version of our app talks to 7.9 ES.

We can't upgrade the app first since Client SDK is not backward compatible. Though we could try testing this combination where we first upgrade the app and then ES (ES SDK 7.9 talks to ES 7.1), but this is not guaranteed to work.

How can we achieve a zero impact, no downtime upgrade easily?  
Any thoughts?

Thanks,  
Pradeep.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 9, 2021, 10:01am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-strategies/263706/2 "2021-03-09T10:01:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.