# Upgrade ElasticSearh from 5.5 to 7.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [February 10, 2020, 12:43pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588 "2020-02-10T12:43:39Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![rahulka](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@rahulka](https://discuss.elastic.co/u/rahulka)\ **Post date:** [February 10, 2020, 12:43pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/1 "2020-02-10T12:43:39Z")
Hi, I am looking to upgrade and migrate from elasticsearch 5.5 to 7.1. Wanted to understand, Is this possible and if yes then do we need to do a rolling update to intermediate version. Also do you have any compatibility matrix between different version. ---
**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:** [February 10, 2020, 1:08pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/2 "2020-02-10T13:08:21Z")
You will need to reindex as data created with a 5.x can't be read as is by a 7.x version. ---
**Author:** ![rahulka](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@rahulka](https://discuss.elastic.co/u/rahulka)\ **Post date:** [February 10, 2020, 1:15pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/3 "2020-02-10T13:15:40Z")
Thanks. But is it possible to upgrade directly from 5.5 to 7.1 version? And when you say reindex, does it mean we have to delete the index (Created following the index pattern) and then recreating them in the newer version? ---
**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:** [February 10, 2020, 2:59pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/4 "2020-02-10T14:59:33Z")
> [@rahulka](#): > > But is it possible to upgrade directly from 5.5 to 7.1 version? No. > [@rahulka](#): > > And when you say reindex, does it mean we have to delete the index (Created following the index pattern) and then recreating them in the newer version? Yes. But you can use the reindex API to help you doing this. Otherwise, you need to: - Upgrade to 5.6.16 - Use the upgrade assistant to check what needs to be done - Upgrade to 6.8.6 - Use the upgrade assistant to check what needs to be done - Upgrade to 7.x. I'd recommend 7.5.2 as this is the latest one. ---
**Author:** ![rahulka](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@rahulka](https://discuss.elastic.co/u/rahulka)\ **Post date:** [February 11, 2020, 8:10am UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/5 "2020-02-11T08:10:15Z")
Thanks @dadoonet for reply and It really help to clarify many stuff. So just to reiterate for my confirmation • Reindex and Upgrade to 5.6.16 •Use the upgrade assistant to check what needs to be done •Upgrade to 6.8.6 •Use the upgrade assistant to check what needs to be done •Upgrade to 7.x. I'd recommend 7.5.2 as this is the latest one. 1. When we are reindexing using api then I believe the will belong to target or destination elastic search. 2. Is it possible to back out the change (back to 5.5 version in case of any issue? Apologies in case my questions are too basic. I will be doing this for the first time? ---
**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:** [February 11, 2020, 1:36pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/6 "2020-02-11T13:36:16Z")
I answered in [Upgrade Rollback](https://discuss.elastic.co/t/upgrade-rollback/218774/2) ---
**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:** [February 11, 2020, 1:37pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/7 "2020-02-11T13:37:10Z")
Using reindex, and specifically reindex from remote feature is helpful to directly go from a old version to a new one and benefit from all the optimisations that happened in the meantime. ---
**Author:** ![rahulka](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@rahulka](https://discuss.elastic.co/u/rahulka)\ **Post date:** [February 12, 2020, 7:19am UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/8 "2020-02-12T07:19:57Z")
when we say reindex, shall we directly reindex to 7.x version or shall we take step wise approach like 1. reindex 5.5 to 5.6, then upgrade 2. reindex 5.6 to 6.8 then upgrade( I don't think reindex is required here as per the documentation, but still correct me if m wrong) 3. reindex 6.8 to 7.x, then upgrade Second approach Directly reindex to 7.x version Secondly can you help me understand the difference in two approaches of upgrade 1: Rolling upgrade 2: Restart upgrade ---
**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:** [February 12, 2020, 7:45am UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/9 "2020-02-12T07:45:04Z")
You need to reindex once you get to 6.8, not while on version 5.x. ---
**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:** [February 12, 2020, 8:18am UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/10 "2020-02-12T08:18:05Z")
I'd probably try this: > [@rahulka](#): > > Second approach > Directly reindex to 7.x version ---
**Author:** ![rahulka](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@rahulka](https://discuss.elastic.co/u/rahulka)\ **Post date:** [February 12, 2020, 9:09am UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/11 "2020-02-12T09:09:32Z")
Thanks both for the answers. Can you please suggest something on the other part of the question, which is "Secondly can you help me understand the difference in two approaches of upgrade" 1: Rolling upgrade 2: Restart upgrade Is it recommended to go for (my understanding by reading the docs though it get confusing at times) 1. 5.5 to 5.6 - rolling upgrade 2. 5.6 to 6.8 - full cluster restart 3. 6.8 to 7.1 - rolling upgrade or can we choose between either of them as it doesn't make much difference. ---
**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:** [February 12, 2020, 10:56am UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/12 "2020-02-12T10:56:56Z")
Full cluster restart means that all nodes are down and you can't serve your users anymore during the shutdown period. But it's safer, easier IMO. Rolling upgrade means that your cluster is still operational while changing the version. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 11, 2020, 10:57am UTC](https://discuss.elastic.co/t/upgrade-elasticsearh-from-5-5-to-7-1/218588/13 "2020-03-11T10:57:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.