Node ” + currentNodes.getLocalNode() + ” not master for join request – Elasticsearch Error How To Solve Related Issues



Node ” + currentNodes.getLocalNode() + ” not master for join request – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 

 

This guide will help you check for common problems that cause the log “Node ” + currentNodes.getLocalNode() + ” not master for join request” 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: node, cluster.


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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”Node [” + currentNodes.getLocalNode() + “] not master for join request”classname  is JoinTaskExecutor.java 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());







Find Configuration Errors

Try The Tool