Failed to remove shard index is closed – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch tries to remove a shard from an index that is already closed. This could be due to a timing issue or a bug in the system. To resolve this issue, you can try reopening the index before removing the shard. Alternatively, you can restart the Elasticsearch node to clear any lingering processes. If the error persists, consider upgrading your Elasticsearch version as it might be a bug that has been fixed in a newer version.

This guide will help you check for common problems that cause the log ” [{}] failed to remove shard (index is closed) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, indices and shard.

Log Context

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

                 for (Integer shardId : indexService.shardIds()) {
                    logger.debug("[{}][{}] removing shard (index is closed)"; index; shardId);
                    try {
                        indexService.removeShard(shardId; "removing shard (index is closed)");
                    } catch (Throwable e) {
                        logger.warn("[{}] failed to remove shard (index is closed)"; e; index);
        for (IndexService indexService : indicesService) {