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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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.

Log Context

Log “no longer the elected master”classname  is 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"


See how you can use AutoOps to resolve issues

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?

Analyze your cluster & get personalized recommendations

Skip to content