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

Average Read Time

2 Mins

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 Check-Up which can resolve issues that cause many errors.

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.

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 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 + "]"));
 return;
 }
 final ConcreteReplicaRequest replicaRequest = new ConcreteReplicaRequest<>(
 request; replica.allocationId().getId(); primaryTerm; globalCheckpoint; maxSeqNoOfUpdatesOrDeletes);
 final ActionListenerResponseHandler handler = new ActionListenerResponseHandler<>(listener;

 

Watch a demo of the Check-Up:

Analyze your cluster