Dangling index. exists on local file system. but not in cluster metadata. timeout set to 0. deleting now – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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;




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content