Local node found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-8

Briefly, this error occurs when Elasticsearch is unable to find a local node in the cluster. This could be due to network issues, incorrect configuration, or the node being down. To resolve this, you can check the network connectivity, ensure the node is running, and verify the configuration settings. If the node is down, restart it. If the configuration is incorrect, correct it and restart Elasticsearch. If the network is the issue, fix the network problem and ensure that the node can communicate with the rest of the cluster.

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

Log Context

Log “local node found” class name is HandshakingTransportAddressConnector.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // success means (amongst other things) that the cluster names match
 logger.trace("[{}] handshake successful: {}"; thisConnectionAttempt; remoteNode);
 IOUtils.closeWhileHandlingException(connection);  if (remoteNode.equals(transportService.getLocalNode())) {
 listener.onFailure(new ConnectTransportException(remoteNode; "local node found"));
 } else if (remoteNode.isMasterNode() == false) {
 listener.onFailure(new ConnectTransportException(remoteNode; "non-master-eligible node found"));
 } else {
 transportService.connectToNode(remoteNode; new ActionListener<>() {


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?