Non-master-eligible node found – Elasticsearch Error How To Solve Related Issues


Non-master-eligible node found – Elasticsearch Error How To Solve Related Issues

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” non-master-eligible node found ” 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 and discovery.

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

Log Context

Log”non-master-eligible node found”classname  is HandshakingTransportAddressConnector.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

IOUtils.closeWhileHandlingException(connection);
 
  if (remoteNode.equals(transportService.getLocalNode())) {
  listener.onFailure(new ConnectTransportException(remoteNode; "local node found"));
  } else if (remoteNode.isMasterNode() == false) {
  listener.onFailure(new ConnectTransportException(remoteNode; "non-master-eligible node found"));
  } else {
  transportService.connectToNode(remoteNode; new ActionListener() {
  @Override
  public void onResponse(Void ignored) {
  logger.trace("[{}] completed full connection with [{}]"; thisConnectionAttempt; remoteNode);

 

Optimize Elasticsearch Performance

Try The Tool