Publication cancelled before committing – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-8.9

Briefly, this error occurs when a node fails to publish a cluster state before it is committed. This could be due to network issues, node failure, or the node being too slow to respond. To resolve this issue, you can try increasing the timeout settings, ensuring the network connectivity is stable, or optimizing the node’s performance. If the problem persists, consider checking the node’s health and logs for any underlying issues.

This guide will help you check for common problems that cause the log ” publication cancelled before committing: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “publication cancelled before committing:” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 assert cancelled == false;
 cancelled = true;
 if (applyCommitRequest.isPresent() == false) {
 logger.debug("cancel: [{}] cancelled before committing (reason: {})"; this; reason);
 // fail all current publications
 final Exception e = new ElasticsearchException("publication cancelled before committing: " + reason); -> pt.setFailed(e));


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?