Node ” + currentNodes.getLocalNode() + ” not master for join request – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

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 ” Node ” + currentNodes.getLocalNode() + ” not master for join request ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node and cluster.

Log Context

Log “Node [” + currentNodes.getLocalNode() + “] not master for join request”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// during the cluster state publishing guarantees that we have enough
 newState = becomeMasterAndTrimConflictingNodes(currentState; joiningNodes);
 nodesChanged = true;
 } else if (currentNodes.isLocalNodeElectedMaster() == false) {
 logger.trace("processing node joins; but we are not the master. current master: {}"; currentNodes.getMasterNode());
 throw new NotMasterException("Node [" + currentNodes.getLocalNode() + "] not master for join request");
 } else {
 newState = ClusterState.builder(currentState);
 DiscoveryNodes.Builder nodesBuilder = DiscoveryNodes.builder(newState.nodes());


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content