Hello together, right now we have a 7 Node Cluster with Version 6.3.0. One Node is only for kibana. Every other Node hast the following options in elasticsearch.yml: node.master: True node.data: True node.ingest: True These are my _cluster/settings: GET _cluster/settings { "persistent": { …

Did you perhaps repurpose the node that was used for Kibana, i.e. was it master- or data-eligible at some point? If so, you've hit https://github.com/elastic/elasticsearch/issues/27073 . If the Kibana node previously contained metadata/data, this can cause this situation. The solution is to clean the…

Discuss the Elastic Stack

DANGLING_INDEX_IMPORTED: How to cleanup old deleted indices

Elastic Stack Elasticsearch

ywelsch (Yannick Welsch) April 5, 2019, 7:36am 4

great, happy to hear that.

Topic		Replies	Views
Dangling indices Elasticsearch	5	613	July 6, 2017
[ES5.6] Unassigned Shards due to DANGLING_INDEX_IMPORTED Elasticsearch	6	801	November 26, 2019
Dangling Index Imported Leads to Unassigned Shards Elasticsearch	19	6363	November 7, 2017
Dangling Index after running Curator Elasticsearch	8	673	August 7, 2018
UNASSIGNED SHARDS and deleted indices coming back Elasticsearch	2	1292	April 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

DANGLING_INDEX_IMPORTED: How to cleanup old deleted indices

Related topics