DANGLING_INDEX_IMPORTED as reason of unassigned shards

Elastic Stack Elasticsearch
1

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.

2

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?

3

After restart cluster and attemp manual allocation of primary shard reason was change to ALLOCATION FAILED because data files were removed.

4

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