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 analyzes 2 JSON files to detect many errors.

Briefly, this error occurs when Elasticsearch is unable to delete a closed index. This can happen when the index is already deleted, or there is a permission issue. To resolve the issue, you should check the Elasticsearch logs to identify the root cause of the error and take appropriate action to fix the problem.

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.

This guide will help you check for common problems that cause the log ” Failed to delete closed index ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, index and indices.

Log Context

Log “[{}] failed to delete closed index” classname is IndicesService.java.
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());
            }
        }
    }

    /**




 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Skip to content