Incoming last accepted 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” incoming last accepted term ” 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 “incoming last accepted term”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final long lastAcceptedTerm = getLastAcceptedTerm();
 if (join.getLastAcceptedTerm() > lastAcceptedTerm) {
 logger.debug("handleJoin: ignored join as joiner has a better last accepted term (expected: <=[{}]; actual: [{}])";
 lastAcceptedTerm; join.getLastAcceptedTerm());
 throw new CoordinationStateRejectedException("incoming last accepted term " + join.getLastAcceptedTerm() +
 " of join higher than current last accepted term " + lastAcceptedTerm);
 if (join.getLastAcceptedTerm() == lastAcceptedTerm && join.getLastAcceptedVersion() > getLastAcceptedVersion()) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content