# Upgrading 1.x to 7.x

**URL:** <https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284>\
**Category:** Elasticsearch\
**Created:** [August 9, 2020, 5:38am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284 "2020-08-09T05:38:35Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tulasinadh\_V](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tulasinadh_v/32/73568_2.png) [@Tulasinadh\_V](https://discuss.elastic.co/u/Tulasinadh_V)\
**Post date:** [August 9, 2020, 5:38am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/1 "2020-08-09T05:38:35Z")

</div>

Hi Team,

My current organization using the Elastic Search 1.x and there was a plan to upgrade it to the latest stable version(7.x). Please suggest the better way to handle this without any downtime

Thanks in advance

---

<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:** [August 9, 2020, 6:08am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/2 "2020-08-09T06:08:06Z")

</div>

I do not think you can do that without downtime but how much downtime will likely depend on the use case and how much data you have got.

---

<div class="post-metadata">

**Author:** ![Tulasinadh\_V](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tulasinadh_v/32/73568_2.png) [@Tulasinadh\_V](https://discuss.elastic.co/u/Tulasinadh_V)\
**Post date:** [August 9, 2020, 6:17am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/3 "2020-08-09T06:17:24Z")

</div>

Around 500GB data is there, how long it may take to migrate.

---

<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:** [August 9, 2020, 6:26am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/4 "2020-08-09T06:26:14Z")

</div>

How long just the reindexing takes will depend on the data and the hardware available. You will need to test.

You will also need to change clients. What is the use case? How are you using Elasticsearch?

---

<div class="post-metadata">

**Author:** ![Tulasinadh\_V](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tulasinadh_v/32/73568_2.png) [@Tulasinadh\_V](https://discuss.elastic.co/u/Tulasinadh_V)\
**Post date:** [August 9, 2020, 6:29am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/5 "2020-08-09T06:29:34Z")

</div>

Using for Java based applications to log user transactions.

---

<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:** [August 9, 2020, 6:32am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/6 "2020-08-09T06:32:49Z")

</div>

Then you will need to change the client library and probably switch to the high level rest client. You may also need to change how you store data as there has been a lot of breaking changes since Elasticsearch 1.x.

---

<div class="post-metadata">

**Author:** ![Tulasinadh\_V](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tulasinadh_v/32/73568_2.png) [@Tulasinadh\_V](https://discuss.elastic.co/u/Tulasinadh_V)\
**Post date:** [August 9, 2020, 6:38am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/7 "2020-08-09T06:38:45Z")

</div>

Thanks for the info @Christian_Dahlqvist  
As of now, it is a managed cluster, there is no objection to migrate to cloud services like (Amazon Elasticsearch Service) and yes libraries also will get updates.

---

<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:** [August 9, 2020, 10:54am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/8 "2020-08-09T10:54:14Z")

</div>

Did you look at [https://www.elastic.co/cloud](https://www.elastic.co/cloud) and [https://aws.amazon.com/marketplace/pp/B01N6YCISK](https://aws.amazon.com/marketplace/pp/B01N6YCISK) ?

Cloud by elastic is one way to have access to all features, all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, APM, Logs UI, Infra UI, SIEM, Maps UI, AppSearch and what is coming next 🙂 ...

---

<div class="post-metadata">

**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:** [August 10, 2020, 5:18am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/9 "2020-08-10T05:18:11Z")

</div>

Your best option would be to spin up a new cluster, then do a [remote reindex](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#reindex-from-remote) to pull the data in.

You will need to adjust mappings for this, along with the other things Christian mentioned.

---

<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:** [September 7, 2020, 5:18am UTC](https://discuss.elastic.co/t/upgrading-1-x-to-7-x/244284/10 "2020-09-07T05:18:30Z")

</div>

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