How To Solve Issues Related to Log – Can not be imported as a dangling index; as an index with the same name and UUID exist in the

How To Solve Issues Related to Log – Can not be imported as a dangling index; as an index with the same name and UUID exist in the

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Can not be imported as a dangling index; as an index with the same name and UUID exist in the” it’s important to understand a few problems related to Elasticsearch concepts dangling, index, indices. See bellow important tips and explanations on these concepts

Log Context

Log”[{}] can not be imported as a dangling index; as an index with the same name and UUID exist in the” classname is DanglingIndicesState.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             for (IndexMetaData indexMetaData : indexMetaDataList) {
                if (metaData.hasIndex(indexMetaData.getIndex().getName())) {
                    logger.warn("[{}] can not be imported as a dangling index; as index with same name already exists in cluster metadata";
                        indexMetaData.getIndex());
                } 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 {
                    logger.info("[{}] dangling index exists on local file system; but not in cluster metadata; " +
                                "auto import to cluster state"; indexMetaData.getIndex());




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 How To Resolve Dangling Indices Err  

Dangling Index Warning In Elasticse  

Github Issue Number 18249

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now