Rejecting ” + request + ” as there is already a leader – 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 ” 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 and cluster.

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 “rejecting ” + request + ” as there is already a leader”classname  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");
 public String toString() {
 return "PreVoteCollector{" +


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content