Failed to mark shard as failed because of – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to mark a shard as failed due to issues like network problems, node failures, or disk space issues. To resolve this, you can try the following: 1) Check the health of your nodes and ensure they are properly connected. 2) Verify that there’s enough disk space available. 3) Check the Elasticsearch logs for more detailed error messages. 4) If a specific shard is consistently problematic, consider reindexing your data.

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.

Log Context

Log “[{}][{}] failed to mark shard as failed (because of [{}])” classname is
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 {


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?