Log Unknown response type ; expected NodeLocalGatewayMetaState or FailedNodeException – How To Solve Related Issues


Log Unknown response type ; expected NodeLocalGatewayMetaState or FailedNodeException – How To Solve Related Issues

Opster Team

Feb-20, 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 that cause many errors.

This guide will help you check for common problems that cause the log ” Unknown response type ; expected NodeLocalGatewayMetaState or FailedNodeException ” 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: node and response.

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

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()]));
    }




 

Optimize Elasticsearch Performance

Try The Tool