Failed to delete shard after failed startup – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.3-1.3

Briefly, this error occurs when Elasticsearch tries to delete a shard after a failed startup but is unable to do so. This could be due to insufficient permissions, disk space issues, or a network problem. To resolve this issue, you can try the following: 1) Check and adjust the permissions of the Elasticsearch directories. 2) Free up disk space or increase the disk capacity. 3) Check the network connectivity and settings. 4) Restart the Elasticsearch service. 5) If the problem persists, consider reindexing the data.

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

Log Context

Log “[{}][{}] failed to delete shard after failed startup” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try {
                    indexService.removeShard(shardRouting.shardId().id(); "recovery failure [" + ExceptionsHelper.detailedMessage(failure) + "]");
                } catch (IndexShardMissingException e) {
                    // the node got closed on us; ignore it
                } catch (Throwable e1) {
                    logger.warn("[{}][{}] failed to delete shard after failed startup"; e1; indexService.index().name(); shardRouting.shardId().id());
            if (sendShardFailure) {
                try {
                    failedShards.put(shardRouting.shardId(); new FailedShard(shardRouting.version()));


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?