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 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 ” Can not be imported as a dangling index; as there is already another index ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: dangling, index and indices.

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 “[{}] 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);




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content