Disconnected – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.3-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch loses connection with the client or the cluster nodes. This could be due to network issues, high load on the Elasticsearch cluster, or the cluster being down. To resolve this, you can check the network connectivity, ensure the Elasticsearch service is running, and monitor the cluster’s health and load. If the load is high, consider optimizing your queries or increasing the cluster’s resources.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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

Log Context

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

 void handleDisconnectedNode(DiscoveryNode discoveryNode) {
 if (discoveryNode.equals(leader)) {
 logger.debug("leader [{}] disconnected"; leader);
 () -> format("master node [%s] disconnected; restarting discovery"; leader.descriptionWithoutAttributes());
 new NodeDisconnectedException(discoveryNode; "disconnected")
 }  private void scheduleNextWakeUp() {


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?

Get expert answers on Elasticsearch/OpenSearch