# DANGLING\_INDEX\_IMPORTED as reason of unassigned shards
**URL:** https://discuss.elastic.co/t/dangling-index-imported-as-reason-of-unassigned-shards/110640
**Category:** Elasticsearch
**Created:** [December 7, 2017, 9:33am UTC](https://discuss.elastic.co/t/dangling-index-imported-as-reason-of-unassigned-shards/110640 "2017-12-07T09:33:01Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@vsevolodk](https://discuss.elastic.co/u/vsevolodk)
#### Post date: [December 7, 2017, 9:33am UTC](https://discuss.elastic.co/t/dangling-index-imported-as-reason-of-unassigned-shards/110640/1 "2017-12-07T09:33:02Z")
Hello.
Can you please give more detailed description about this reason DANGLING\_INDEX\_IMPORTED
In documentation I see next
`Unassigned as a result of importing a dangling index.` but I don't understand what does it mean.
---
### Author:  [@vsevolodk](https://discuss.elastic.co/u/vsevolodk)
#### Post date: [December 7, 2017, 11:22am UTC](https://discuss.elastic.co/t/dangling-index-imported-as-reason-of-unassigned-shards/110640/2 "2017-12-07T11:22:29Z")
After cluster restart, reason now is CLUSTER\_RECOVERED and for some shard I have
`"final_explanation": "the copy of the shard is stale, allocation ids do not match"`
How can I recover (?corrupted) shards?
---
### Author:  [@vsevolodk](https://discuss.elastic.co/u/vsevolodk)
#### Post date: [December 7, 2017, 3:16pm UTC](https://discuss.elastic.co/t/dangling-index-imported-as-reason-of-unassigned-shards/110640/3 "2017-12-07T15:16:34Z")
After restart cluster and attemp manual allocation of primary shard reason was change to ALLOCATION FAILED because data files were removed.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 4, 2018, 3:16pm UTC](https://discuss.elastic.co/t/dangling-index-imported-as-reason-of-unassigned-shards/110640/4 "2018-01-04T15:16:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.