Log Failed to delete shard after failed startup – How To Solve Related Issues


Log Failed to delete shard after failed startup – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to delete shard after failed startup ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, delete, indices and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “[{}][{}] failed to delete shard after failed startup” classname is IndicesClusterStateService.java
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()));




 

Optimize Elasticsearch Performance

Try The Tool