[WARN ][o.e.g.DanglingIndicesState] [X] - can not be imported as a dangling index, as index with same name already exists in cluster metadata

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)

  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.

How do you shutdown your cluster?

I installed elasticsearch using docker (docker.elastic.co/elasticsearch/elasticsearch:5.6.2) and I use docker stop (or docker-compose 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).

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