Handshake failed. unexpected remote node – How to solve this Elasticsearch error

Average Read Time

2 Mins

Handshake failed. unexpected remote node – 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 ” handshake failed. unexpected remote node ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: 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 “handshake failed. unexpected remote node”classname  is TransportService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return (newConnection; actualProfile; listener) -> {
 // We don't validate cluster names to allow for CCS connections.
 handshake(newConnection; actualProfile.getHandshakeTimeout().millis(); cn -> true; ActionListener.map(listener; resp -> {
 final DiscoveryNode remote = resp.discoveryNode;
 if (node.equals(remote) == false) {
 throw new ConnectTransportException(node; "handshake failed. unexpected remote node " + remote);
 }
 return null;
 }));
 };
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content