Found dangled index on node . This index cannot be – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Found dangled index on node . This index cannot be ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: dangled, index, indices and node.

Log Context

Log “Found dangled index [{}] on node [{}]. This index cannot be” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             // with the current version and upgrade it if needed.
                            upgradedIndexMetaData = metaDataIndexUpgradeService.upgradeIndexMetaData(indexMetaData;
                        } catch (Exception ex) {
                            // upgrade failed - adding index as closed
                            logger.warn(() -> new ParameterizedMessage("found dangled index [{}] on node [{}]. This index cannot be " +
                                "upgraded to the latest version; adding as closed"; indexMetaData.getIndex(); request.fromNode); ex);
                            upgradedIndexMetaData = IndexMetaData.builder(indexMetaData).state(IndexMetaData.State.CLOSE)
                                .version(indexMetaData.getVersion() + 1).build();
                        metaData.put(upgradedIndexMetaData; false);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content