Election not won – 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 become a master but fails. This could be due to network issues, configuration problems, or a higher-priority node taking over. To resolve this, ensure all nodes are properly configured and network connectivity is stable. Also, check the master node’s priority settings. If necessary, adjust the ‘discovery.zen.minimum_master_nodes’ setting to avoid split-brain scenarios.

This guide will help you check for common problems that cause the log ” election not won ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “election not won” class name 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");