Failed to mark shard as failed after a failed engine () – How to solve related issues

Failed to mark shard as failed after a failed engine () – 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 after a failed engine () ” 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 (free tool that requires no installation).

Log Context

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

                         }
                        try {
                            failedShards.put(fShardRouting.shardId(); new FailedShard(fShardRouting.version()));
                            shardStateAction.shardFailed(fShardRouting; indexUUID; failureMessage);
                        } catch (Throwable e1) {
                            logger.warn("[{}][{}] failed to mark shard as failed after a failed engine ([{}])"; e1; indexService.index().name(); shardId.id(); reason);
                        }
                    }
                }
            });
        }




 

Run the Check-Up to get a customized report like this:

Analyze your cluster