Action ” + action + ” not found – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Action ” + action + ” not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Action [” + action + “] not found”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try {
 onRequestSent(localNode; requestId; action; request; options);
 onRequestReceived(requestId; action);
 final RequestHandlerRegistry reg = getRequestHandler(action);
 if (reg == null) {
 throw new ActionNotFoundTransportException("Action [" + action + "] not found");
 final String executor = reg.getExecutor();
 if (ThreadPool.Names.SAME.equals(executor)) {
 //noinspection unchecked
 reg.processMessageReceived(request; channel);


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content