No longer leading this publication’s term: – How to solve this Elasticsearch error

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 Error 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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


Run the Check-Up to get a customized report like this:

Analyze your cluster