Incoming term – 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 ” incoming term ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

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

 public Join handleStartJoin(StartJoinRequest startJoinRequest) {
 if (startJoinRequest.getTerm() <= getCurrentTerm()) {
 logger.debug("handleStartJoin: ignoring [{}] as term provided is not greater than current term [{}]";
 startJoinRequest; getCurrentTerm());
 throw new CoordinationStateRejectedException("incoming term " + startJoinRequest.getTerm() +
 " not greater than current term " + getCurrentTerm());
 logger.debug("handleStartJoin: leaving term [{}] due to {}"; getCurrentTerm(); startJoinRequest);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content