Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Dangling index. exists on local file system. but not in cluster metadata. timeout set to 0. deleting now ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, dangling and discovery-file.
Log Context
Log “[{}] dangling index; exists on local file system; but not in cluster metadata; timeout set to 0; deleting now” classname is LocalGatewayMetaState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (indexMetaData != null) {
if(autoImportDangled.shouldImport()){
logger.info("[{}] dangling index; exists on local file system; but not in cluster metadata; auto import to cluster state [{}]"; indexName; autoImportDangled);
danglingIndices.put(indexName; new DanglingIndex(indexName; null));
} else if (danglingTimeout.millis() == 0) {
logger.info("[{}] dangling index; exists on local file system; but not in cluster metadata; timeout set to 0; deleting now"; indexName);
indicesService.deleteIndexStore("dangling index with timeout set to 0"; indexMetaData; state);
} else {
logger.info("[{}] dangling index; exists on local file system; but not in cluster metadata; scheduling to delete in [{}]; auto import to cluster state [{}]"; indexName; danglingTimeout; autoImportDangled);
danglingIndices.put(indexName;
new DanglingIndex(indexName;
