OnFollowerCheckRequest: current term is – How to solve this Elasticsearch error

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” onFollowerCheckRequest: current term is ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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


Run the Check-Up to get a customized report like this:

Analyze your cluster