Failed to remove shard disabled block persistence – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to remove the shard block that prevents write operations due to some internal issues. This could be due to a lack of disk space, network issues, or a problem with the Elasticsearch cluster itself. To resolve this issue, you can try freeing up disk space, checking your network connections, or restarting your Elasticsearch cluster. Additionally, you may need to check your cluster health and ensure that all nodes are functioning properly.

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)");


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?