Failed to send join request to master – 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 analyzes 2 JSON files to detect many errors.

Briefly, this error message typically occurs in a multi-node Elasticsearch cluster when a node is unable to join the cluster because it cannot communicate with the master node. The issue can be caused by a variety of factors, including network connectivity issues, firewall rules, or misconfigured settings. To resolve the issue, you can start by verifying the network connectivity between the nodes and checking that the Elasticsearch configuration is correct.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Failed to send join request to master ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, join, master and request.

Log Context

Log “Failed to send join request to master [{}]; reason [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                } else {
                    if (logger.isTraceEnabled()) {
                        logger.trace(() -> new ParameterizedMessage("failed to send join request to master [{}]"; masterNode); e);
                    } else {
              "failed to send join request to master [{}]; reason [{}]"; masterNode;
                    return false;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content