Incoming last accepted version – How to solve this Elasticsearch error

Average Read Time

2 Mins

Incoming last accepted version – 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 version ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: version and 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 version”classname  is CoordinationState.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content