Rejecting request as there is already a leader – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-8.9

Briefly, this error occurs when a node in Elasticsearch tries to elect itself as a leader, but a leader already exists in the cluster. This is a part of Elasticsearch’s built-in mechanism to prevent data inconsistencies. To resolve this issue, ensure that the cluster’s nodes are properly communicating. If a node is isolated or network partitioning has occurred, it might falsely believe there is no leader. Also, check the cluster’s health and settings. If the error persists, consider restarting the nodes or the entire cluster, but be aware this may cause temporary unavailability.

This guide will help you check for common problems that cause the log ” rejecting ” + request + ” as there is already a leader ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request, cluster.

Log Context

Log “rejecting ” + request + ” as there is already a leader” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // leader won't change; and also that its re-election will happen more quickly than if it had to wait for a quorum of followers
 // to also detect its failure.
 return response;
 }  throw new CoordinationStateRejectedException("rejecting " + request + " as there is already a leader");
 }  @Override
 public String toString() {
 return "PreVoteCollector{" + "state=" + state + '}';