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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when the master node in a cluster is no longer available or is unable to perform its duties. This can happen when the master node goes down or when the cluster is being reconfigured. To resolve the issue, check the status of the master node and the cluster, ensure there is enough disk space, and manually elect a new master node if necessary.

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 ” 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.

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()) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content