OnFollowerCheckRequest: current term is – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

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

Log Context

Log “onFollowerCheckRequest: current term is [“classname  is Coordinator.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

synchronized (mutex) {
 ensureTermAtLeast(followerCheckRequest.getSender(); followerCheckRequest.getTerm()); 
 if (getCurrentTerm() != followerCheckRequest.getTerm()) {
 logger.trace("onFollowerCheckRequest: current term is [{}]; rejecting {}"; getCurrentTerm(); followerCheckRequest);
 throw new CoordinationStateRejectedException("onFollowerCheckRequest: current term is ["
 + getCurrentTerm() + "]; rejecting " + followerCheckRequest);
 // check if node has accepted a state in this term already. If not; this node has never committed a cluster state in this
 // term and therefore never removed the NO_MASTER_BLOCK for this term. This logic ensures that we quickly turn a node


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content