Handshake failed because connection reset – How to solve this Elasticsearch error

Average Read Time

2 Mins

Handshake failed because connection reset – 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 because connection reset ” 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 because connection reset”classname  is TransportHandshaker.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

void sendHandshake(long requestId; DiscoveryNode node; TcpChannel channel; TimeValue timeout; ActionListener listener) {
 numHandshakes.inc();
 final HandshakeResponseHandler handler = new HandshakeResponseHandler(requestId; version; listener);
 pendingHandshakes.put(requestId; handler);
 channel.addCloseListener(ActionListener.wrap(
 () -> handler.handleLocalException(new TransportException("handshake failed because connection reset"))));
 boolean success = false;
 try {
 // for the request we use the minCompatVersion since we don't know what's the version of the node we talk to
 // we also have no payload on the request but the response will contain the actual version of the node we talk
 // to as the payload.

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content