Became follower – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when a node in an Elasticsearch cluster changes its role from a leader to a follower. This can happen due to network issues, resource constraints, or configuration changes. To resolve this, you can check the cluster’s health and configuration. Ensure all nodes are properly connected and configured. If resource constraints are the issue, consider scaling up your cluster or optimizing your queries and indices to reduce resource usage. If the problem persists, you may need to manually reassign the leader role.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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

Log Context

Log “became follower” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }; joiningTerm);
 } else {
 assert newMode == Mode.FOLLOWER : newMode;
 .forEach(joinCallback -> joinCallback.v2().onFailure(new CoordinationStateRejectedException("became follower")));
 }  // CandidateJoinAccumulator is only closed when becoming leader or follower; otherwise it accumulates all joins received
 // regardless of term.


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?