How To Solve Issues Related to Log – Failed to delete closed index

How To Solve Issues Related to Log – Failed to delete closed index

Updated: Feb-20

Elasticsearch Version: 1.7-8.0


Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.

To troubleshoot log “Failed to delete closed index” it’s important to understand a few problems related to Elasticsearch concepts delete, index, indices. See bellow important tips and explanations on these concepts

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());


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Failed To Delete Indices When Curat  

Failed To Delete Index  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now