Unknown response type ; expected NodeStoreFilesMetaData 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 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.

This guide will help you check for common problems that cause the log ” Unknown response type ; expected NodeStoreFilesMetaData or FailedNodeException ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, node, response and shard.

Log Context

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

             if (resp instanceof NodeStoreFilesMetaData) { // will also filter out null response for unallocated ones
                nodeStoreFilesMetaDatas.add((NodeStoreFilesMetaData) resp);
            } else if (resp instanceof FailedNodeException) {
                failures.add((FailedNodeException) resp);
            } else {
                logger.warn("unknown response type [{}]; expected NodeStoreFilesMetaData or FailedNodeException"; resp);
        return new NodesStoreFilesMetaData(clusterName; nodeStoreFilesMetaDatas.toArray(new NodeStoreFilesMetaData[nodeStoreFilesMetaDatas.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?

Analyze your cluster & get personalized recommendations

Skip to content