Failed to delete closed index – How to solve related issues

Average Read Time

2 Mins

Failed to delete closed index – How to solve related issues

Opster Team

Feb-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 ” Failed to delete closed index ” 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: delete, index and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “[{}] failed to delete closed index” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     final IndexMetaData index = clusterState.metaData().index(indexName);
                    throw new IllegalStateException("Can't delete closed index store for [" + indexName + "] - it's still part of the cluster state [" + index.getIndexUUID() + "] [" + metaData.getIndexUUID() + "]");
                deleteIndexStore(reason; metaData; clusterState; true);
            } catch (IOException e) {
                logger.warn("[{}] failed to delete closed index"; e; metaData.getIndex());



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

Analyze your cluster