Unknown response type expected NodeLocalGatewayMetaState or FailedNodeException – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch expects a response type of either NodeLocalGatewayMetaState or FailedNodeException, but receives something different. This could be due to a version mismatch between nodes, a corrupted cluster state, or a network issue. To resolve this, you can try restarting the nodes, ensuring all nodes are running the same version of Elasticsearch, or checking the network connectivity between nodes. If the cluster state is corrupted, you may need to restore it from a backup.

This guide will help you check for common problems that cause the log ” unknown response type [{}]; expected NodeLocalGatewayMetaState or FailedNodeException ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node and response.

Log Context

Log “unknown response type [{}]; expected NodeLocalGatewayMetaState or FailedNodeException” classname is TransportNodesListGatewayMetaState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             if (resp instanceof NodeGatewayMetaState) { // will also filter out null response for unallocated ones
                nodesList.add((NodeGatewayMetaState) resp);
            } else if (resp instanceof FailedNodeException) {
                failures.add((FailedNodeException) resp);
            } else {
                logger.warn("unknown response type [{}]; expected NodeLocalGatewayMetaState or FailedNodeException"; resp);
        return new NodesGatewayMetaState(clusterName; nodesList.toArray(new NodeGatewayMetaState[nodesList.size()]);
                failures.toArray(new FailedNodeException[failures.size()]));


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?