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 “Dangling index exists on local file system; but not 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, discovery-file, 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. 

                 } 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());
                } else {
                    logger.info("[{}] dangling index exists on local file system; but not in cluster metadata; " +
                                "auto import to cluster state"; indexMetaData.getIndex());
                    newIndices.put(indexMetaData.getIndex(); indexMetaData);
                }
            }
            return newIndices;

Find Configuration Errors

Try The Tool