Ignoring dangled index on node due to an existing alias with the same name – 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 ” Ignoring dangled index on node due to an existing alias with the same name ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: alias, dangled, index, indices and node.

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 “Ignoring dangled index [{}] on node [{}] due to an existing alias with the same name” classname is LocalAllocateDangledIndices.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         }
                        if (currentState.metaData().hasIndex(indexMetaData.getIndex().getName())) {
                            continue;
                        }
                        if (currentState.metaData().hasAlias(indexMetaData.getIndex().getName())) {
                            logger.warn("ignoring dangled index [{}] on node [{}] due to an existing alias with the same name";
                                    indexMetaData.getIndex(); request.fromNode);
                            continue;
                        }
                        importNeeded = true;





 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content