How To Solve Issues Related to Log – Dangling index exists on local file system; but not in cluster metadata;

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)


Last update: Jan-20

Elasticsearch Error Guide In Page Navigation (click to jump) :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check Your Elasticsearch Settings for Painfull Mistakes 

Troubleshooting background

To troubleshoot Elasticsearch log “Dangling index exists on local file system; but not in cluster metadata;” it’s important to know common problems related to Elasticsearch concepts: cluster, dangling, discovery-file, index, indices. See below-detailed explanations complete with common problems, examples and useful tips.

Cluster in Elasticsearch

What is it

In Elasticsearch a cluster is a collection of one or more nodes (servers / VMs). A cluster can consist of an unlimited number of nodes. The cluster provides interface for indexing and storing data and search capability across all of the data which is stored in the data nodes

Each cluster has a single master node that is elected by the master eligible nodes. In cases where the master is not available the other connected master eligible nodes elect a new master. Clusters are identified by a unique name, which defaults to “Elasticsearch”.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1. Why deleted indexes appear when I restart the elasticsearch? – Stats : ♥ 1.57 K  Ι √ –

2. Indices Red – Stats : ♥ 0.38 K  Ι √     –

Log Context

Log ”Dangling index exists on local file system; but not in cluster metadata;” classname is
We have extracted the following from Elasticsearch source code to get an in-depth context :

                 } else if (graveyard.containsIndex(indexMetaData.getIndex())) {
                    logger.warn("[{}] can not be imported as a dangling index; as an index with the same name and UUID exist in the " +
                                "index tombstones.  This situation is likely caused by copying over the data directory for an index " +
                                "that was previously deleted."; indexMetaData.getIndex());
                } else {
          "[{}] dangling index exists on local file system; but not in cluster metadata; " +
                                "auto import to cluster state"; indexMetaData.getIndex());
                    newIndices.put(indexMetaData.getIndex(); indexMetaData);
            return newIndices;

About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?