Log Failed to connect to master ; retrying. – How To Solve Related Issues


Log Failed to connect to master ; retrying. – How To Solve Related Issues

Opster Team

Dec-19, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the 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. ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: discovery-azure-classic.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 {

 





Optimize Elasticsearch Performance

Try The Tool