Log Can not be imported as a dangling index; as there is already another index – How To Solve Related Issues



Log Can not be imported as a dangling index; as there is already another index – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Can not be imported as a dangling index; as there is already another index” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: dangling, index, indices.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log “[{}] can not be imported as a dangling index; as there is already another index” classname is DanglingIndicesState.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     void cleanupAllocatedDangledIndices(MetaData metaData) {
        for (Index index : danglingIndices.keySet()) {
            final IndexMetaData indexMetaData = metaData.index(index);
            if (indexMetaData != null && indexMetaData.getIndex().getName().equals(index.getName())) {
                if (indexMetaData.getIndex().getUUID().equals(index.getUUID()) == false) {
                    logger.warn("[{}] can not be imported as a dangling index; as there is already another index " +
                        "with the same name but a different uuid. local index will be ignored (but not deleted)"; index);
                } else {
                    logger.debug("[{}] no longer dangling (created); removing from dangling list"; index);
                }
                danglingIndices.remove(index);









Find Configuration Errors

Try The Tool