Can not be imported as a dangling index, as index with same name already exists in cluster metadata – How to solve related issues

Can not be imported as a dangling index, as index with same name already exists in cluster metadata – How to solve related issues

Opster Team

Feb-21, Version: 1.7-8.0

To understand why an index cannot be important as a dangling index because another with the same name already exisits in the cluster metadata, we commend you run this Elasticsearch Error Check-Up which can help you resolve the issue and prevent others from occuring.

This guide will help you check for common problems that cause the log “Cannot be imported as a dangling index, as index with same name already exists in cluster metadata” 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: cluster, dangling, index, indices and metadata.


quick Overview

When you get this log it means that a cluster is trying to import a stale index.
How to solve:

1. Call GET _cat/indices?v and find UUID column. These UUIDs should match directory names inside node data path under “nodes/0/indices”. Otherwise, these directories are dangling indices. That the node is trying to import.

2. For every dangling index, you can move them out of this nodes/0/indices into the same directory structure of a new Elasticsearch node installation. This will result in having two nodes. You can decide which node you want to keep.

Log Context

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

             final List indexMetaDataList = metaStateService.loadIndicesStates(excludeIndexPathIds::contains);
            Map newIndices = new HashMap(indexMetaDataList.size());
            final IndexGraveyard graveyard = metaData.indexGraveyard();
            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());




 

Run the Check-Up to get a customized report like this:

Analyze your cluster