Failed to connect to master ; retrying. (version 6.8) – How to solve related issues

Average Read Time

2 Mins

Failed to connect to master ; retrying. (version 6.8) – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to connect to master ; retrying. (version 6.8) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery and master.

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 “Failed to connect to master [{}]; retrying…” classname is ZenDiscovery.java.
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
            transportService.connectToNode(masterNode);
        } 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 {




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content