Failed to remove shard (disabled block persistence) – 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.

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 remove shard (disabled block persistence) ” 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 (disabled block persistence)” 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 (disabled block persistence)"; index; shardId);
                        try {
                            indexService.removeShard(shardId; "removing shard (disabled block persistence)");
                        } catch (Throwable e) {
                            logger.warn("[{}] failed to remove shard (disabled block persistence)"; e; index);
                    removeIndex(index; "cleaning index (disabled block persistence)");


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content