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

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Feb-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

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


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 :

 

2How To Resolve Dangling Indices Err  


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 have extracted the following from Elasticsearch source code to get 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);






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