Election not won – Elasticsearch Error How To Solve Related Issues

Election not won – 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 “election not won” 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: 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”election not won”classname  is CoordinationState.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

* @throws CoordinationStateRejectedException if the arguments were incompatible with the current state of this object.
  public PublishRequest handleClientValue(ClusterState clusterState) {
  if (electionWon == false) {
  logger.debug("handleClientValue: ignored request as election not won");
  throw new CoordinationStateRejectedException("election not won");
  if (lastPublishedVersion != getLastAcceptedVersion()) {
  logger.debug("handleClientValue: cannot start publishing next value before accepting previous one");
  throw new CoordinationStateRejectedException("cannot start publishing next value before accepting previous one");


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 Nodes won't join cluster : NotMasterException (Weird master election bug) -views 2,765 ,score 5

Elasticsearch 7.2.0: master not discovered or elected yet, an election requires at least X nodes -views   465,score 1



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now