Disconnected – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.3-8.9

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.

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() {