# \[WARN \]\[o.e.g.DanglingIndicesState\] \[X\] - can not be imported as a dangling index, as index with same name already exists in cluster metadata
**URL:** https://discuss.elastic.co/t/warn-o-e-g-danglingindicesstate-x-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/102756
**Category:** Elasticsearch
**Created:** [October 4, 2017, 8:24pm UTC](https://discuss.elastic.co/t/warn-o-e-g-danglingindicesstate-x-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/102756 "2017-10-04T20:24:54Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@alexus](https://discuss.elastic.co/u/alexus)
#### Post date: [October 4, 2017, 8:24pm UTC](https://discuss.elastic.co/t/warn-o-e-g-danglingindicesstate-x-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/102756/1 "2017-10-04T20:24:54Z")
whenever I start my cluster, my logs produces _a lot_ of these messages (just different name for index):
> elasticsearch11 | [2017-10-04T20:20:44,936][WARN][o.e.g.DanglingIndicesState] [114ff04a775b] [[.monitoring-es-6-2017.09.30/zCVhEla1Q9yo4MRCeTeZww]] can not be imported as a dangling index, as index with same name already exists in cluster metadata
I asked similar question a while ago ([Can not be imported as a dangling index as index with same name already exists in cluster metadata - Elasticsearch - Discuss the Elastic Stack](https://discuss.elastic.co/t/can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/89455/))
1. What I can do to avoid this from happening in the future?
2. What is better way to handle this? (especially in production environment)
Thanks in advance.
---
### Author:  [@mujtabahussain](https://discuss.elastic.co/u/mujtabahussain)
#### Post date: [October 4, 2017, 10:38pm UTC](https://discuss.elastic.co/t/warn-o-e-g-danglingindicesstate-x-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/102756/2 "2017-10-04T22:38:34Z")
> [@](#):
>
> whenever I start my cluster
How do you shutdown your cluster?
---
### Author:  [@alexus](https://discuss.elastic.co/u/alexus)
#### Post date: [October 5, 2017, 1:30am UTC](https://discuss.elastic.co/t/warn-o-e-g-danglingindicesstate-x-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/102756/3 "2017-10-05T01:30:16Z")
I installed elasticsearch using _docker_ ([docker.elastic.co/elasticsearch/elasticsearch:5.6.2](http://docker.elastic.co/elasticsearch/elasticsearch:5.6.2)) and I use [docker stop](https://docs.docker.com/engine/reference/commandline/stop/) (or [docker-compose stop](https://docs.docker.com/compose/reference/stop/)) to stop container(s).
Please correct me if I'm wrong, however I don't believe there is anything else to do (see: [Nodes shutdown | Elasticsearch Reference [5.5] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/cluster-nodes-shutdown.html)).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 2, 2017, 1:31am UTC](https://discuss.elastic.co/t/warn-o-e-g-danglingindicesstate-x-can-not-be-imported-as-a-dangling-index-as-index-with-same-name-already-exists-in-cluster-metadata/102756/4 "2017-11-02T01:31:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.