# Upgrade 2.x

**URL:** <https://discuss.elastic.co/t/upgrade-2-x/64912>\
**Category:** Elasticsearch\
**Created:** [November 3, 2016, 4:52pm UTC](https://discuss.elastic.co/t/upgrade-2-x/64912 "2016-11-03T16:52:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![genesis](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@genesis](https://discuss.elastic.co/u/genesis)\
**Post date:** [November 3, 2016, 4:52pm UTC](https://discuss.elastic.co/t/upgrade-2-x/64912/1 "2016-11-03T16:52:08Z")

</div>

After upgrading from 1.7.1 to 2.4.1 Elasticsearch is starting but port 9200 is down I am seeing lots of messages like these in the logs. Any idea what is going on?  
[2016-11-03 16:42:47,449][INFO][common.util] [myindex-2016.11.01][3] syncing [\_20d6\_Lucene410\_0.dvm]  
[2016-11-03 16:42:47,452][INFO][common.util] [myindex-2016.11.01][3] syncing [\_20d6.fdx]  
[2016-11-03 16:42:47,459][INFO][common.util] [myindex-2016.11.01][3] syncing [\_20d6\_Lucene41\_0.tip]  
[2016-11-03 16:42:47,535][INFO][common.util] [myindex-2016.11.01][3] syncing [\_2iaa.fdx]  
[2016-11-03 16:42:47,538][INFO][common.util] [myindex-2016.11.01][3] syncing [\_2iaa\_Lucene41\_0.tip]  
[2016-11-03 16:42:47,553][INFO][common.util] [myindex-2016.11.01][3] syncing directory [/var/data/elasticsearch2/Media/nodes/0/indices/myindex-2016.11.01/3/index]  
[2016-11-03 16:42:47,553][INFO][common.util] [myindex-2016.11.01][3] upgrading [translog] from [/var/data/elasticsearch/Media/nodes/0/indices/myindex-2016.11.01/3/translog] to [/var/data/elasticsearch2/Media/nodes/0/indices/myindex-2016.11.01/3/translog]  
[2016-11-03 16:42:47,553][INFO][common.util] [myindex-2016.11.01][3] wipe upgraded directories  
[2016-11-03 16:42:47,553][INFO][common.util] [myindex-2016.11.01][3] wipe shard directories: [/var/data/elasticsearch/Media/nodes/0/indices/myindex-2016.11.01/3]

---

<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:** [November 4, 2016, 8:49am UTC](https://discuss.elastic.co/t/upgrade-2-x/64912/2 "2016-11-04T08:49:17Z")

</div>

> [@genesis](#):
>
> Elasticsearch is starting but port 9200 is down

That seems unlikely. What does the rest of your log look like?

---

<div class="post-metadata">

**Author:** ![Tarun\_Hasija](https://avatars.discourse-cdn.com/v4/letter/t/a698b9/32.png) [@Tarun\_Hasija](https://discuss.elastic.co/u/Tarun_Hasija)\
**Post date:** [November 8, 2016, 5:53pm UTC](https://discuss.elastic.co/t/upgrade-2-x/64912/3 "2016-11-08T17:53:10Z")

</div>

Hi we are seeing the same scenario @genesis. The data only nodes are performing some kind of syncing and the cluster is staying in red status for a long time. This is causing a very long downtime due to the upgrade

---

<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:** [July 5, 2017, 10:06pm UTC](https://discuss.elastic.co/t/upgrade-2-x/64912/4 "2017-07-05T22:06:05Z")

</div>