Failed to receive message for action – 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 analyzes 2 JSON files to detect many 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. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Failed to receive message for action ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Index and Memory.

Log Context

Log “Failed to receive message for action [” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 TransportResponseHandler handler = transportServiceAdapter.onResponseReceived(sendRequestId);
                if (handler != null) {
                    handleException(handler; new RemoteTransportException(nodeName(); localAddress; action; e));
            } else {
                logger.warn("Failed to receive message for action [" + action + "]"; e);

    private void handleRequest(StreamInput stream; long requestId; LocalTransport sourceTransport; Version version) throws Exception {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content