No longer the elected master – How to solve this Elasticsearch error

Average Read Time

2 Mins

No longer the elected master – How to solve this Elasticsearch error

Opster Team

March-22, 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 ” no longer the elected master ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, master.

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 “no longer the elected master”classname  is LeaderChecker.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (statusInfo.getStatus() == UNHEALTHY) {
 logger.debug("this node is unhealthy [{}]; rejecting leader check: {}"; statusInfo.getInfo(); request);
 throw new NodeHealthCheckFailureException(statusInfo.getInfo());
 } else if (discoveryNodes.isLocalNodeElectedMaster() == false) {
 logger.debug("rejecting leader check on non-master: {}"; request);
 throw new CoordinationStateRejectedException("no longer the elected master");
 } else if (discoveryNodes.nodeExists(request.getSender()) == false) {
 logger.debug("rejecting leader check from removed node: {}"; request);
 throw new CoordinationStateRejectedException(
 "rejecting check since [" + request.getSender().descriptionWithoutAttributes() + "] has been removed from the cluster"
 );

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content