# Upgrade elasticsearch

**URL:** <https://discuss.elastic.co/t/upgrade-elasticsearch/249491>\
**Category:** Elasticsearch\
**Created:** [September 22, 2020, 9:34am UTC](https://discuss.elastic.co/t/upgrade-elasticsearch/249491 "2020-09-22T09:34:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![blomqc](https://avatars.discourse-cdn.com/v4/letter/b/439d5e/32.png) [@blomqc](https://discuss.elastic.co/u/blomqc)\
**Post date:** [September 22, 2020, 9:34am UTC](https://discuss.elastic.co/t/upgrade-elasticsearch/249491/1 "2020-09-22T09:34:15Z")

</div>

after upgrading elasticsearch binaries from 1.7.x to 2.x, elasticsearch takes very long (~20h) get back online.  
From the log it looks like data is moved around ?  
Only seen this issue when elasticsearch is configured with multiple data path. Can someone explain what elasticsearch is doing? Is there a way avoiding this or speed up this process?

`[2020-09-12 00:16:30,967][INFO][common.util] [167679467122275144_-1833138985_201608_031-2][3] upgrading multi data dir to G:\ESDATA\esclusterdev\nodes\0\indices\167679467122275144_-1833138985_201608_031-2\3`  
`[2020-09-12 00:16:30,967][INFO][common.util] [167679467122275144_-1833138985_201608_031-2][3] loaded shard state version [18], primary [true]`  
`[2020-09-12 00:16:30,983][INFO][common.util] [167679467122275144_-1833138985_201608_031-2][3] upgrading [index] from [F:\ESDATA\esclusterdev\nodes\0\indices\167679467122275144_-1833138985_201608_031-2\3\index] to [G:\ESDATA\esclusterdev\nodes\0\indices\167679467122275144_-1833138985_201608_031-2\3\index]`  
`[2020-09-12 00:16:30,983][INFO][common.util] [167679467122275144_-1833138985_201608_031-2][3] move file [segments.gen] size: [36]`  
`[2020-09-12 00:16:30,999][INFO][common.util] [167679467122275144_-1833138985_201608_031-2][3] move file [segments_w] size: [1857]`  
`[2020-09-12 00:16:31,014][INFO][common.util] [167679467122275144_-1833138985_201608_031-2][3] move file [_1a.cfe] size: [350]`  
`[2020-09-12 00:16:31,014][INFO][common.util] [1676794671`

thanks in advance

thanks

---

<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:** [September 22, 2020, 10:21pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearch/249491/2 "2020-09-22T22:21:55Z")

</div>

Do you mean that recovery after a node/cluster restart takes this long?  
How many nodes and shards are you looking at? What size of data?

Also 2.X has been [EOL](https://www.elastic.co/support/eol) for quite some time now, you should upgrade as a matter of urgency.

---

<div class="post-metadata">

**Author:** ![blomqc](https://avatars.discourse-cdn.com/v4/letter/b/439d5e/32.png) [@blomqc](https://discuss.elastic.co/u/blomqc)\
**Post date:** [September 25, 2020, 10:58am UTC](https://discuss.elastic.co/t/upgrade-elasticsearch/249491/3 "2020-09-25T10:58:54Z")

</div>

Yes, exactly after the restart. Two data nodes one master, 680 shards and total 3.5TB. Yeah, this cluster is bit behind on versions and upgrade is in progress.

---

<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:** [September 28, 2020, 12:34am UTC](https://discuss.elastic.co/t/upgrade-elasticsearch/249491/4 "2020-09-28T00:34:33Z")

</div>

Older versions of Elasticsearch did take quite some time to recover. Upgrading is your best option.

---

<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:** [October 26, 2020, 12:34am UTC](https://discuss.elastic.co/t/upgrade-elasticsearch/249491/5 "2020-10-26T00:34:51Z")

</div>

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