# Broken after upgrade from ES 1.4.x to 2.4.x

**URL:** <https://discuss.elastic.co/t/broken-after-upgrade-from-es-1-4-x-to-2-4-x/75977>\
**Category:** Elasticsearch\
**Created:** [February 22, 2017, 3:53am UTC](https://discuss.elastic.co/t/broken-after-upgrade-from-es-1-4-x-to-2-4-x/75977 "2017-02-22T03:53:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ultimate.duwal](https://avatars.discourse-cdn.com/v4/letter/u/2acd7d/32.png) [@ultimate.duwal](https://discuss.elastic.co/u/ultimate.duwal)\
**Post date:** [February 22, 2017, 3:53am UTC](https://discuss.elastic.co/t/broken-after-upgrade-from-es-1-4-x-to-2-4-x/75977/1 "2017-02-22T03:53:49Z")

</div>

I have a cluster with 7 nodes (6 data nodes, 1 query node) with 3 TB/4 TB Disk size filled. Where, each nodes are attached with 14 disks of 50 GB each.

I tried to upgrade a smaller index of about 100 GB from ES 1.4.0 to 2.4.4 and was successful with it. After that I tried to upgrade the 3TB data but it got stuck at upgrading a index.  
And seems the data is now broken while upgrade is stuck. What should I do?

Also what would be the approximate time it takes to upgrade from ES 1.x to 2.x. ? Experimenting with the upgrade, it took me about 45 mins for upgrading 100 GBs of data in that configuration.

---

<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:** [March 22, 2017, 3:53am UTC](https://discuss.elastic.co/t/broken-after-upgrade-from-es-1-4-x-to-2-4-x/75977/2 "2017-03-22T03:53:58Z")

</div>

Closed on March 22, 2017, 3:53am UTC

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