Ignored join as term has not been incremented yet after reboot – How to solve this Elasticsearch error

Average Read Time

2 Mins

Ignored join as term has not been incremented yet after reboot – 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 ” ignored join as term has not been incremented yet after reboot ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: join 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 “ignored join as term has not been incremented yet after reboot”classname  is CoordinationState.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

"incoming term " + join.getTerm() + " does not match current term " + getCurrentTerm());
 } 
 if (startedJoinSinceLastReboot == false) {
 logger.debug("handleJoin: ignored join as term was not incremented yet after reboot");
 throw new CoordinationStateRejectedException("ignored join as term has not been incremented yet after reboot");
 } 
 final long lastAcceptedTerm = getLastAcceptedTerm();
 if (join.getLastAcceptedTerm() > lastAcceptedTerm) {
 logger.debug("handleJoin: ignored join as joiner has a better last accepted term (expected: <=[{}]; actual: [{}])";

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content