Became follower – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

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


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content