Non-master-eligible node found – How to solve this Elasticsearch error

Average Read Time

2 Mins

Non-master-eligible node found – 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 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. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

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);

 

Watch a demo of the Check-Up:

Analyze your cluster