Failed to delete shard after ignore recovery – 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 ignoring its recovery but fails. This could be due to insufficient permissions, disk space issues, or network connectivity problems. To resolve this, you can try increasing disk space, checking network connectivity, or adjusting the user permissions. Additionally, you may need to manually delete the shard if it’s not being used, or try restarting the Elasticsearch node to clear any temporary issues.

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

Log Context

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

try {
                        indexService.removeShard(shardRouting.shardId().id(); "ignore recovery: " + reason);
                    } catch (IndexShardMissingException e) {
                        // the node got closed on us; ignore it
                    } catch (Throwable e1) {
                        logger.warn("[{}][{}] failed to delete shard after ignore recovery"; e1; indexService.index().name(); shardRouting.shardId().id());


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?