# Warning can not be imported as a dangling index, as index with same name already exists in cluster metadata
**URL:** https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577
**Category:** Elasticsearch
**Created:** [September 16, 2019, 5:41am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577 "2019-09-16T05:41:17Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Nikhil\_Pillai](https://discuss.elastic.co/u/Nikhil_Pillai)
#### Post date: [September 16, 2019, 5:41am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577/1 "2019-09-16T05:41:17Z")
I am running ELK 6.5.4 with 3 node cluster. Cluster health is GREEN
I see below error in one of the node.
```auto
[2019-09-16T11:05:49,832][WARN][o.e.g.DanglingIndicesState] [node-3] [[.watcher-history-9-2019.07.12/1fkhSke8S7CQVA8TJZ5GHg]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
[2019-09-16T11:05:49,833][WARN][o.e.g.DanglingIndicesState] [node-3] [[genie-zipkin:span-2019-08-26/J2CNO0MbRsmj8W5OcuVBPQ]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
```
How do i resolve the same without deleting the index from the cluster.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 16, 2019, 5:45am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577/2 "2019-09-16T05:45:05Z")
How have you ended up in this situation? Have you experienced a network partition, e.g. by having more than one master eligible node and having minimum\_master\_nodes not set to `2`?
---
### Author:  [@Nikhil\_Pillai](https://discuss.elastic.co/u/Nikhil_Pillai)
#### Post date: [September 16, 2019, 6:01am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577/3 "2019-09-16T06:01:21Z")
by having more than one master eligible node and having minimum\_master\_nodes not set to `2`
-- Yes but now minimum\_master\_nodes is set to 2.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 16, 2019, 6:03am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577/4 "2019-09-16T06:03:43Z")
Did this issue occur when minimum\_master\_nodes was set to `2` or when it was changed to `2`?
---
### Author:  [@Nikhil\_Pillai](https://discuss.elastic.co/u/Nikhil_Pillai)
#### Post date: [September 16, 2019, 6:09am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577/5 "2019-09-16T06:09:09Z")
No the issue existed before minimum\_master\_nodes was set to 2
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 16, 2019, 6:10am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577/6 "2019-09-16T06:10:23Z")
OK, then it is likely due to a network partition. In that case I do not think there is anything you can do but to accept the data loss that may have occurred to do this misconfiguration.
---
### Author:  [@Nikhil\_Pillai](https://discuss.elastic.co/u/Nikhil_Pillai)
#### Post date: [September 16, 2019, 6:13am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577/7 "2019-09-16T06:13:05Z")
i am getting this warning only on one node. So if i delete the index from that node can i reduce the data loss or do i have to delete the index completely from the cluster?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 14, 2019, 6:13am UTC](https://discuss.elastic.co/t/warning-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/199577/8 "2019-10-14T06:13:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.