Log Failed to mark shard as failed (because of ) – How To Solve Related Issues



Log Failed to mark shard as failed (because of ) – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Failed to mark shard as failed (because of ) ” 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, 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. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

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





Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Fail To Assign Shards After Restart

2 Github Issue Number 37888






Optimize Elasticsearch Performance

Try The Tool