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

Opster Team

August-23, Version: 7-8

Briefly, this error occurs when a node in the Elasticsearch cluster is not eligible to become a master node. This could be due to incorrect configuration settings. To resolve this issue, you can check the node’s configuration in the elasticsearch.yml file. Ensure that the ‘node.master’ setting is set to true. If the issue persists, consider checking the cluster’s health and network connectivity. Also, ensure that the cluster has enough master-eligible nodes to prevent split-brain scenarios.

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: discovery, node.

Log Context

Log “non-master-eligible node found” class name is 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<>() {
 public void onResponse(Releasable connectionReleasable) {
 logger.trace("[{}] completed full connection with [{}]"; thisConnectionAttempt; remoteNode);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?