# Upgrade from 1.7 to 5.5

**URL:** <https://discuss.elastic.co/t/upgrade-from-1-7-to-5-5/93752>\
**Category:** Elasticsearch\
**Created:** [July 19, 2017, 11:35am UTC](https://discuss.elastic.co/t/upgrade-from-1-7-to-5-5/93752 "2017-07-19T11:35:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanketdarji](https://avatars.discourse-cdn.com/v4/letter/s/76d3ee/32.png) [@sanketdarji](https://discuss.elastic.co/u/sanketdarji)\
**Post date:** [July 19, 2017, 11:35am UTC](https://discuss.elastic.co/t/upgrade-from-1-7-to-5-5/93752/1 "2017-07-19T11:35:40Z")

</div>

need some help in upgrading elsticsearch 1.7 to 5.5 in single VM enviroment

I want to upgrade my production elasticsearch 1.7 version to 5.5 version  
-\> I found out the below links [https://www.elastic.co/guide/en/elasticsearch/reference/current/reindex-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/reindex-upgrade.html)

Here we have 2 options:  
I wanted to go with Upgrading with reindex-from-remote but issue what faced is we have only one VM.

I will not able to install new elasticsearch-5.5 because we have 1.7 installed .

Can you please suggest me how can I upgrade elasticseach from 1.7 to 5.5 without losing my data in single VM?

---

<div class="post-metadata">

**Author:** ![Comradin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/comradin/32/19339_2.png) [@Comradin](https://discuss.elastic.co/u/Comradin)\
**Post date:** [July 19, 2017, 1:16pm UTC](https://discuss.elastic.co/t/upgrade-from-1-7-to-5-5/93752/2 "2017-07-19T13:16:04Z")

</div>

Hi,

as the document states, you should take the first option and update to 2.4.x in the first place and reindex the existing indices. After this you can do the switch to 5.5.

If you insist on using the single jump update with the reindex-from-remote, you have to install the elasticsearch 5.5.0 release with custom port/cluster/data.path settings on the same machine and run them side by side. But be prepared for issues, as this will require lots of memory.

---

<div class="post-metadata">

**Author:** ![sanketdarji](https://avatars.discourse-cdn.com/v4/letter/s/76d3ee/32.png) [@sanketdarji](https://discuss.elastic.co/u/sanketdarji)\
**Post date:** [July 20, 2017, 10:49am UTC](https://discuss.elastic.co/t/upgrade-from-1-7-to-5-5/93752/3 "2017-07-20T10:49:50Z")

</div>

Thanks Comradin, I tried upgrading to 2.4 (then will move to 5.5 ).  
And I am using Elasticsearch Migration Plugin for re-indexing.  
Issue I am facing with existing indices:

curl -XGET 'localhost:9200/\_cat/indices?v&pretty'  
health status index pri rep docs.count docs.deleted store.size pri.store.size  
yellow open .kibana 5 1 9 0 41.3kb 41.3kb  
yellow open logstash-2017.07.20 5 1 2148 0 634.5kb 634.5kb  
yellow open .reindex-status 1 1 0 0 159b 159b

It is show health for all indices as yellow and plugin will not work until it moves to green.  
What it the reason for yellow status of indices.

Can you please help in this how can I re-index my existing indexes.

---

<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:** [August 17, 2017, 10:57am UTC](https://discuss.elastic.co/t/upgrade-from-1-7-to-5-5/93752/4 "2017-08-17T10:57:09Z")

</div>

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