# Upgrade from ES 1.7 to ES 2.4 leads to loss of data **URL:** \ **Category:** Elasticsearch\ **Created:** [June 5, 2017, 6:07am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-7-to-es-2-4-leads-to-loss-of-data/88225 "2017-06-05T06:07:00Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mosiddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mosiddi/32/577_2.png) [@mosiddi](https://discuss.elastic.co/u/mosiddi)\ **Post date:** [June 5, 2017, 6:07am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-7-to-es-2-4-leads-to-loss-of-data/88225/1 "2017-06-05T06:07:00Z")
Hi, We have moved from ES 1.7 to ES 2.4 over a period of last 1 year in all our ES clusters. What we observed in some of our 1-node cluster is while upgrading from ES 1.7 to ES 2.4, all indices and aliases are gone. The steps (in simplified words) for upgrade are - - Stop ES 1.7 - Uninstall ES 1.7 - Install ES 2.4 pointing to same data folder as ES 1.7 - Start ES 2.4 On further investigations, we noticed the data (from ES 1.7) was in [cluster name / nodes / **0**] folder while the ES 2.4 is storing the data in [cluster name / nodes / **1**] folder. Any idea when this can happen and how to fix this issue? Thanks Imran ---
**Author:** ![mosiddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mosiddi/32/577_2.png) [@mosiddi](https://discuss.elastic.co/u/mosiddi)\ **Post date:** [June 5, 2017, 6:07am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-7-to-es-2-4-leads-to-loss-of-data/88225/2 "2017-06-05T06:07:42Z")
The folder under "nodes" folder - ![](https://us1.discourse-cdn.com/elastic/original/3X/e/6/e6d554f8dfc5516eb3afee076b356b6b0cd9176b.png) ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 5, 2017, 7:54am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-7-to-es-2-4-leads-to-loss-of-data/88225/3 "2017-06-05T07:54:41Z")
It means that you started 2 nodes at the same time on the same machine. In 5.0 this is not possible anymore BTW. ---
**Author:** ![mosiddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mosiddi/32/577_2.png) [@mosiddi](https://discuss.elastic.co/u/mosiddi)\ **Post date:** [June 5, 2017, 8:12am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-7-to-es-2-4-leads-to-loss-of-data/88225/4 "2017-06-05T08:12:44Z")
Thanks! We ensured in our code that we wait for ES 1.7 uninstall to complete before installing ES 2.4. I'll check the same again. Also, do we need to wait for anything in particular when we say ES 1.7 is indeed uninstalled? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 5, 2017, 4:42pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-7-to-es-2-4-leads-to-loss-of-data/88225/5 "2017-06-05T16:42:24Z")
Did you run a ps -ef ? I mean that elasticsearch 2.4 seemed to think that node 0 dir was locked by another instance. ---
**Author:** ![mosiddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mosiddi/32/577_2.png) [@mosiddi](https://discuss.elastic.co/u/mosiddi)\ **Post date:** [June 6, 2017, 3:37am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-7-to-es-2-4-leads-to-loss-of-data/88225/6 "2017-06-06T03:37:31Z")
I see, thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 4, 2017, 3:48am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-7-to-es-2-4-leads-to-loss-of-data/88225/7 "2017-07-04T03:48:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.