Publication failed – 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 ” publication failed ” 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 “publication failed”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public void onFailure(Exception e) {
 assert Thread.holdsLock(mutex) : "Coordinator mutex not held";
 final FailedToCommitClusterStateException exception = new FailedToCommitClusterStateException("publication failed"; e);
 ackListener.onNodeAck(getLocalNode(); exception); // other nodes have acked; but not the master.
 }; EsExecutors.newDirectExecutorService(); transportService.getThreadPool().getThreadContext());


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content