# Elasticsearch ignores old data after upgrade from 1.7.3 to 2.3.0

**URL:** <https://discuss.elastic.co/t/elasticsearch-ignores-old-data-after-upgrade-from-1-7-3-to-2-3-0/47663>\
**Category:** Elasticsearch\
**Created:** [April 18, 2016, 1:43pm UTC](https://discuss.elastic.co/t/elasticsearch-ignores-old-data-after-upgrade-from-1-7-3-to-2-3-0/47663 "2016-04-18T13:43:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chelovek\_Chelovechni](https://avatars.discourse-cdn.com/v4/letter/c/9d8465/32.png) [@Chelovek\_Chelovechni](https://discuss.elastic.co/u/Chelovek_Chelovechni)\
**Post date:** [April 18, 2016, 1:43pm UTC](https://discuss.elastic.co/t/elasticsearch-ignores-old-data-after-upgrade-from-1-7-3-to-2-3-0/47663/1 "2016-04-18T13:43:32Z")

</div>

First, I've tried this on local machine.

1. Installed ES 1.7.3
2. Populated it with some production data
3. Installed ES migration plugin
4. Reindexed data and deleted old indices, so migration plugin showed that everything is ok
5. Upgraded ES to 2.3.0
6. Restarted ES

Everything worked and I was able to query all indices.

I used the exact same procedure to upgrade ES in production. Unfortunately, there are issues.

Elasticsearch 2.3.0 is green and running, but it ignores indices. Currently it shows only 3 indices - 2 for marvel and 1 for kibana. I'm sure that data dir is correct - these indices stored in the same place as old ones.

Logs show "dangling index directory detected, but no state found" for each old index.

What should I do?

---

<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:58pm UTC](https://discuss.elastic.co/t/elasticsearch-ignores-old-data-after-upgrade-from-1-7-3-to-2-3-0/47663/2 "2017-07-05T22:58:29Z")

</div>

Closed on July 5, 2017, 10:58pm UTC