No longer leading this publication’s 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 ” no longer leading this publication’s 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 “no longer leading this publication’s term:”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

logger.trace("handlePublishRequest: handling [{}] from [{}]"; publishRequest; sourceNode); 
 if (sourceNode.equals(getLocalNode()) && mode != Mode.LEADER) {
 // Rare case in which we stood down as leader between starting this publication and receiving it ourselves. The publication
 // is already failed so there is no point in proceeding.
 throw new CoordinationStateRejectedException("no longer leading this publication's term: " + publishRequest);
 final ClusterState localState = coordinationState.get().getLastAcceptedState(); 
 if (localState.metadata().clusterUUIDCommitted() &&


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content