Node is no longer master for 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 ” node is no longer master for term ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node, master 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 “node is no longer master for term”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try {
 synchronized (mutex) {
 if (mode != Mode.LEADER || getCurrentTerm() != clusterChangedEvent.state().term()) {
 logger.debug(() -> new ParameterizedMessage("[{}] failed publication as node is no longer master for term {}";
 clusterChangedEvent.source(); clusterChangedEvent.state().term()));
 publishListener.onFailure(new FailedToCommitClusterStateException("node is no longer master for term " +
 clusterChangedEvent.state().term() + " while handling publication"));
 if (currentPublication.isPresent()) {


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content