Rejecting ” + request + ” as there is already a leader – How to solve this Elasticsearch error

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 Error 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”rejecting ” + request + ” as there is already a leader”classname  is PreVoteCollector.java 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{" +

 

Run the Check-Up to get a customized report like this:

Analyze your cluster