# Does it take a long time for upgrading elasticsearch version 1.4.4 to version 2.4.4?

**URL:** <https://discuss.elastic.co/t/does-it-take-a-long-time-for-upgrading-elasticsearch-version-1-4-4-to-version-2-4-4/63100>\
**Category:** Elasticsearch\
**Created:** [October 15, 2016, 11:25am UTC](https://discuss.elastic.co/t/does-it-take-a-long-time-for-upgrading-elasticsearch-version-1-4-4-to-version-2-4-4/63100 "2016-10-15T11:25:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mover](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@mover](https://discuss.elastic.co/u/mover)\
**Post date:** [October 15, 2016, 11:25am UTC](https://discuss.elastic.co/t/does-it-take-a-long-time-for-upgrading-elasticsearch-version-1-4-4-to-version-2-4-4/63100/1 "2016-10-15T11:25:24Z")

</div>

when i uprading my elasticsearch cluster from 1.4.4 to 2.4.4, i wait for a long time and the nodes do not setup cluster.

i use netstat to check listening port, and i find all nodes do not listem port 9300 and 9200

in the log, there are many log messages like:

[2016-10-15 19:22:22,559][INFO][common.util] [netflow\_log\_v3-sin01-2016.08.03][4] move file [\_1oo\_es090\_0.blm] size: [332878]

[2016-10-15 19:22:52,597][INFO][common.util] [netflow\_log\_v3-sin01-2016.08.03][4] fsync files  
[2016-10-15 19:22:52,597][INFO][common.util] [netflow\_log\_v3-sin01-2016.08.03][4] syncing [segments.gen]  
[2016-10-15 19:22:52,597][INFO][common.util] [netflow\_log\_v3-sin01-2016.08.03][4] syncing [\_26h\_es090\_0.doc]

are there some errors ? or it is normal?

---

<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:** [October 15, 2016, 7:58pm UTC](https://discuss.elastic.co/t/does-it-take-a-long-time-for-upgrading-elasticsearch-version-1-4-4-to-version-2-4-4/63100/2 "2016-10-15T19:58:34Z")

</div>

Looks normal.

How long is a "long time"?

---

<div class="post-metadata">

**Author:** ![mover](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@mover](https://discuss.elastic.co/u/mover)\
**Post date:** [October 16, 2016, 2:08am UTC](https://discuss.elastic.co/t/does-it-take-a-long-time-for-upgrading-elasticsearch-version-1-4-4-to-version-2-4-4/63100/3 "2016-10-16T02:08:30Z")

</div>

yes, it looks like needing to make some data format transformations if upgrading 1.4.4 to 2.4.1.

i started the cluster at about time 19:00 yesterday, and when i checked it on morning of today, the cluster had setup!

---

<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:02pm UTC](https://discuss.elastic.co/t/does-it-take-a-long-time-for-upgrading-elasticsearch-version-1-4-4-to-version-2-4-4/63100/4 "2016-11-08T17:02:20Z")

</div>

Hi  
What is exactly happening on data only nodes when it is moving and fsyncing files ? We are seeing the similar issue and the back to service time for the cluster is very high because of this. Is there a way the progress can be monitored ?

---

<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/does-it-take-a-long-time-for-upgrading-elasticsearch-version-1-4-4-to-version-2-4-4/63100/5 "2017-07-05T22:06:07Z")

</div>