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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when the connection between the client and the Elasticsearch cluster was reset during the handshake process. This could be due to a variety of reasons such as network connectivity issues or problems with the client’s network configuration. You will need to resolve the issue to establish a successful connection.

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.

Take a self-guided product tour to see for yourself (no registration required).

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.

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) {
 final HandshakeResponseHandler handler = new HandshakeResponseHandler(requestId; version; listener);
 pendingHandshakes.put(requestId; handler);
 () -> 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 product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content