Operation ” + actionName + ” failed – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” operation ” + actionName + ” failed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: broadcast and node.

Log Context

Log “operation ” + actionName + ” failed”classname  is TransportBroadcastByNodeAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (logger.isTraceEnabled()) {
 logger.trace("[{}] completed operation for shard [{}]"; actionName; shardRouting.shortSummary());
 } catch (Exception e) {
 BroadcastShardOperationFailedException failure =
 new BroadcastShardOperationFailedException(shardRouting.shardId(); "operation " + actionName + " failed"; e);
 shardResults[shardIndex] = failure;
 if (TransportActions.isShardNotAvailableException(e)) {
 if (logger.isTraceEnabled()) {
 logger.trace(new ParameterizedMessage(


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content