Failed to remove shard (index is closed) – How to solve related issues

Failed to remove shard (index is closed) – 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 remove shard (index is closed) ” 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: cluster, indices and shard.

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 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) {


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

Analyze your cluster