Opster Team
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. ” to appear. To understand the issues related to this log, read the explanation below about the following 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 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 {
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 3 minutes
Arpit Ghiya
Senior Lead SRE at Coupa