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

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Dec-19

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Failed to connect to master ; retrying.” it’s important to understand common problems related to Elasticsearch concepts: discovery-azure-classic. See detailed explanations below complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Connection Timeout To Master For Ne  

 


Log Context

Log ”Failed to connect to master [{}]; retrying…” classname is ZenDiscovery.java
We have extracted the following from Elasticsearch source code to get 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 {



About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster