I have unassigned shards in my cluster, execute: GET /_cluster/allocation/explain result: { "index": "error-log-2018-05-05", "shard": 3, "primary": true, "current_state": "unassigned", "unassigned_info": { "reason": "DANGLING_INDEX_IMPORTED", "at": "2018-08-30T10:11:44.011Z", …

Delete unassigned DANGLING_INDEX_IMPORTED shards

lunatic (Steven) September 3, 2018, 4:25am 2

Solved at Endless creating index after delete another index

Topic		Replies	Views
DANGLING_INDEX_IMPORTED as reason of unassigned shards Elasticsearch	3	1051	January 4, 2018
How can I delete unnassigned shards? Elasticsearch	2	10458	April 7, 2023
ES 6.2.1 Unassigned shards due to DANGLING_INDEX_IMPORTED Elasticsearch	4	1582	April 19, 2018
Dangling Index Imported Leads to Unassigned Shards Elasticsearch	19	6242	November 7, 2017
Dangling_index_imported Elasticsearch	2	1239	September 8, 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.

Delete unassigned DANGLING_INDEX_IMPORTED shards

Related topics