Unknown response type ; expected NodeSnapshotStatus 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 run 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 NodeSnapshotStatus or FailedNodeException ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, cluster, node, response and snapshot.

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 “unknown response type [{}]; expected NodeSnapshotStatus or FailedNodeException” classname is TransportNodesSnapshotsStatus.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content