Unknown node ” + nodeId + ” – How to solve this Elasticsearch error

Opster Team

July-20, 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.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” unknown node ” + nodeId + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: replication and node.

Log Context

Log “unknown node [” + nodeId + “]”classname  is TransportReplicationAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final long maxSeqNoOfUpdatesOrDeletes;
 final ActionListener listener) {
 String nodeId = replica.currentNodeId();
 final DiscoveryNode node = clusterService.state().nodes().get(nodeId);
 if (node == null) {
 listener.onFailure(new NoNodeAvailableException("unknown node [" + nodeId + "]"));
 final ConcreteReplicaRequest replicaRequest = new ConcreteReplicaRequest<>(
 request; replica.allocationId().getId(); primaryTerm; globalCheckpoint; maxSeqNoOfUpdatesOrDeletes);
 final ActionListenerResponseHandler handler = new ActionListenerResponseHandler<>(listener;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content