Failed to delete shard after failed engine () – 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 delete shard after failed engine () ” 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 engine ([{}])” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                indexService.removeShard(; failureMessage);
                            } catch (IndexShardMissingException e) {
                                // the node got closed on us; ignore it
                            } catch (Throwable e1) {
                                logger.warn("[{}][{}] failed to delete shard after failed engine ([{}])"; e1; indexService.index().name();; reason);
                        try {
                            failedShards.put(fShardRouting.shardId(); new FailedShard(fShardRouting.version()));
                            shardStateAction.shardFailed(fShardRouting; indexUUID; failureMessage);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content