# Migration of ES from v2.x to v5.0 without full cluster restart

**URL:** <https://discuss.elastic.co/t/migration-of-es-from-v2-x-to-v5-0-without-full-cluster-restart/68151>\
**Category:** Elasticsearch\
**Created:** [December 6, 2016, 9:49am UTC](https://discuss.elastic.co/t/migration-of-es-from-v2-x-to-v5-0-without-full-cluster-restart/68151 "2016-12-06T09:49:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nikhil\_R](https://avatars.discourse-cdn.com/v4/letter/n/ed655f/32.png) [@Nikhil\_R](https://discuss.elastic.co/u/Nikhil_R)\
**Post date:** [December 6, 2016, 9:49am UTC](https://discuss.elastic.co/t/migration-of-es-from-v2-x-to-v5-0-without-full-cluster-restart/68151/1 "2016-12-06T09:49:20Z")

</div>

From the ES documentation here [https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html) says we require a full cluster restart for an upgrade.  
Is there a way to upgrade a cluster without downtime i.e is there a way of a rolling upgrade?

---

<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:** [December 6, 2016, 9:49am UTC](https://discuss.elastic.co/t/migration-of-es-from-v2-x-to-v5-0-without-full-cluster-restart/68151/2 "2016-12-06T09:49:55Z")

</div>

Nope.

---

<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 6, 2016, 10:53am UTC](https://discuss.elastic.co/t/migration-of-es-from-v2-x-to-v5-0-without-full-cluster-restart/68151/3 "2016-12-06T10:53:31Z")

</div>

But ou can create a fresh new 5.0 cluster and then use reindex from remote to read from 2.x indices.

Of course you will need to stop index operations at some point or to send them to the new cluster instead but it depends on your constraints I guess.

---

<div class="post-metadata">

**Author:** ![Nikhil\_R](https://avatars.discourse-cdn.com/v4/letter/n/ed655f/32.png) [@Nikhil\_R](https://discuss.elastic.co/u/Nikhil_R)\
**Post date:** [December 6, 2016, 11:23am UTC](https://discuss.elastic.co/t/migration-of-es-from-v2-x-to-v5-0-without-full-cluster-restart/68151/4 "2016-12-06T11:23:50Z")

</div>

How does a Production cluster with a 50 -100 node deployment run a upgrade like this?

---

<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 6, 2016, 3:14pm UTC](https://discuss.elastic.co/t/migration-of-es-from-v2-x-to-v5-0-without-full-cluster-restart/68151/5 "2016-12-06T15:14:11Z")

</div>

It means you have to run an equivalent 50 - 100 nodes 5.0 cluster in parallel.  
May be not possible. In which case you have to stop the service, upgrade, then start again. So with downtime.

---

<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:** [January 3, 2017, 3:14pm UTC](https://discuss.elastic.co/t/migration-of-es-from-v2-x-to-v5-0-without-full-cluster-restart/68151/6 "2017-01-03T15:14:32Z")

</div>

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