Publication currentPublication get already in progress – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.16-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when an Elasticsearch node tries to publish a cluster state that is already being published. This could be due to a network issue, a slow node, or a bug in the Elasticsearch software. To resolve this issue, you can try restarting the node, checking the network for any issues, or upgrading Elasticsearch to the latest version. If the problem persists, consider increasing the cluster state publishing timeout settings.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” publication ” + currentPublication.get() + ” already in progress ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “publication ” + currentPublication.get() + ” already in progress” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 () -> format(
 "[%s] failed publication as already publication in progress";
 throw new FailedToCommitClusterStateException("publication " + currentPublication.get() + " already in progress");
 }  assert assertPreviousStateConsistency(clusterStatePublicationEvent);  final ClusterState clusterState;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?