Failed to mark shard as failed after a failed start – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.3-1.3

Briefly, this error occurs when Elasticsearch is unable to mark a shard as failed after an unsuccessful start. This could be due to issues like insufficient disk space, network connectivity problems, or corrupted indices. To resolve this, you can try freeing up disk space, checking your network connections, or repairing the corrupted indices. If the problem persists, consider restarting the Elasticsearch node or increasing the timeout settings.

This guide will help you check for common problems that cause the log ” [{}][{}] failed to mark shard as failed after a failed start ” 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 after a failed start” classname is IndicesClusterStateService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (sendShardFailure) {
                try {
                    failedShards.put(shardRouting.shardId(); new FailedShard(shardRouting.version()));
                    shardStateAction.shardFailed(shardRouting; indexMetaData.getUUID(); "Failed to start shard; message [" + detailedMessage(failure) + "]");
                } catch (Throwable e1) {
                    logger.warn("[{}][{}] failed to mark shard as failed after a failed start"; e1; indexService.index().name(); shardRouting.id());
                }
            }
        }
    }

 

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?