No node meta data at – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” No node meta data at ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, index, node.

Log Context

Log “No node meta data at”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

private void printRerouteCommand(ShardPath shardPath; Terminal terminal; boolean allocateStale) throws IOException {
 final Path nodePath = getNodePath(shardPath);
 final NodeMetadata nodeMetadata = PersistedClusterStateService.nodeMetadata(nodePath); 
 if (nodeMetadata == null) {
 throw new ElasticsearchException("No node meta data at " + nodePath);
 final String nodeId = nodeMetadata.nodeId();
 final String index = shardPath.getShardId().getIndexName();
 final int id = shardPath.getShardId().id();


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content