Election stopped source – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

Briefly, this error occurs when an Elasticsearch node stops participating in the master election process due to a specific reason denoted by the “source”. This could be due to network issues, configuration errors, or resource constraints. To resolve this, you can check the node’s logs for more details about the “source” of the stoppage. Ensure that the node’s network connectivity is stable, its configuration is correct, and it has sufficient resources (CPU, memory, disk space) to operate effectively. Also, verify the cluster’s health and settings.

This guide will help you check for common problems that cause the log ” election stopped [” + source + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, source.

Log Context

Log “election stopped [” + source + “]” class name is NodeJoinController.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public void clusterStateProcessed(String source; ClusterState oldState; ClusterState newState) {
 if (newState.nodes().isLocalNodeElectedMaster()) {
 } else {
 onFailure(source; new NotMasterException("election stopped [" + source + "]"));
 }  @Override
 public void onFailure(String source; Exception e) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?