Index is closed – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.3-8.9

Briefly, this error occurs when an Elasticsearch index is closed and you’re trying to perform operations on it. A closed index has almost no overhead on the cluster except for maintaining its metadata. To resolve this issue, you can either open the index using the ‘open index’ API or delete the index if it’s no longer needed. Alternatively, you can create a new index and reindex the data if the closed index is not recoverable.

This guide will help you check for common problems that cause the log ” Index [{}] is closed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

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

        if (metadata == null) {
            logger.debug("Index [{}] is not available - no metadata"; aliasName);
            return false;
        if (metadata.getState() == IndexMetadata.State.CLOSE) {
            logger.warn("Index [{}] is closed"; aliasName);
            return false;
        final IndexRoutingTable routingTable = state.routingTable().index(metadata.getIndex());
        if (routingTable == null || routingTable.allPrimaryShardsActive() == false) {
            logger.debug("Index [{}] is not yet active"; aliasName);


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?