Rejecting ” + request + ” as there is already a leader – Elasticsearch Error How To Solve Related Issues



Rejecting ” + request + ” as there is already a leader – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing 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, 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 discover the cause of many errors and provides suitable actionable recommendations (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{" +

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Failed to join cluster – Elasticsearch – Discuss the Elastic Stack  

Failed to join cluster – Elasticsearch – Discuss the Elastic Stack  



Find Configuration Errors

Analyze Now