Marking and sending shard failed due to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch encounters an issue with a specific shard, marking it as failed and attempting to resend it. This could be due to a variety of reasons such as network issues, disk space problems, or corruption of the shard. To resolve this, you can try to restart the Elasticsearch node, check for network connectivity issues, ensure there is enough disk space, or restore the shard from a backup. If the shard is corrupted and there’s no backup, you may need to reindex your data.

This guide will help you check for common problems that cause the log ” [{}] marking and sending shard failed due to [{}] ” 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 “[{}] marking and sending shard failed due to [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    private void sendFailShard(ShardRouting shardRouting; String indexUUID; String message; 
Nullable Throwable failure) {
        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);


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?