Operation ” + actionName + ” failed – Elasticsearch Error How To Solve Related Issues

Operation ” + actionName + ” failed – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “operation ” + actionName + ” failed” 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: broadcast, node.

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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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(


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 How do you send pre-made Query object to NEST? -views 691 ,score 1

ElasticSearch stops responding after reaching a certain number of …  



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now