Failed to mark shard as failed (because of ) – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to mark shard as failed (because of ) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, indices and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “[{}][{}] failed to mark shard as failed (because of [{}])” classname is IndicesClusterStateService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         try {
            logger.warn("[{}] marking and sending shard failed due to [{}]"; failure; shardRouting.shardId(); message);
            failedShards.put(shardRouting.shardId(); new FailedShard(shardRouting.version()));
            shardStateAction.shardFailed(shardRouting; indexUUID; message; failure);
        } catch (Throwable e1) {
            logger.warn("[{}][{}] failed to mark shard as failed (because of [{}])"; e1; shardRouting.getIndex(); shardRouting.getId(); message);
        }
    }

    private class FailedEngineHandler implements Engine.FailedEngineListener {
        
Override



 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content