Local node found – 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.

Briefly, this error occurs when Elasticsearch is unable to load settings from a specific location. The solution to this error is to check the location of the settings and ensure that they are accessible and correctly configured.

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 ” local node found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node and discovery.


Log Context

Log “local node found”classname  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<>() {
 @Override

 

See how you can use AutoOps to resolve issues


How useful 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