Failed to connect to master retrying – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.17

Briefly, this error occurs when the Elasticsearch node is unable to connect to the master node. This could be due to network issues, the master node being down, or configuration errors. To resolve this, ensure that the master node is up and running, check the network connectivity between the nodes, and verify the cluster settings in the Elasticsearch configuration file. If the master node is overloaded, consider adding more master-eligible nodes to the cluster to distribute the load.

This guide will help you check for common problems that cause the log ” failed to connect to master [{}]; retrying… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: master, discovery.

Log Context

Log “failed to connect to master [{}]; retrying…” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    private boolean joinElectedMaster(DiscoveryNode masterNode) {
        try {
            // first; make sure we can connect to the master
        } catch (Exception e) {
            logger.warn(() -> new ParameterizedMessage("failed to connect to master [{}]; retrying..."; masterNode); e);
            return false;
        int joinAttempt = 0; // we retry on illegal state if the master is not yet ready
        while (true) {
            try {


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?