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; auto import to cluster state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, dangling, discovery-file and indices.
Log Context
Log “[{}] dangling index; exists on local file system; but not in cluster metadata; auto import to cluster state” classname is DanglingIndicesState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
for (String indexName : indices) {
if (metaData.hasIndex(indexName) == false && danglingIndices.containsKey(indexName) == false) {
try {
IndexMetaData indexMetaData = metaStateService.loadIndexState(indexName);
if (indexMetaData != null) {
logger.info("[{}] dangling index; exists on local file system; but not in cluster metadata; auto import to cluster state"; indexName);
if (!indexMetaData.getIndex().equals(indexName)) {
logger.info("dangled index directory name is [{}]; state name is [{}]; renaming to directory name"; indexName; indexMetaData.getIndex());
indexMetaData = IndexMetaData.builder(indexMetaData).index(indexName).build();
}
newIndices.put(indexName; indexMetaData);
Find & fix Elasticsearch problems
