Failed to publish new cluster state with rollup metadata – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.11-8.2

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 Elasticsearch fails to update the cluster state with rollup metadata, which is used for summarizing and storing historical data. This could be due to network issues, insufficient permissions, or a problem with the rollup job itself. To resolve this issue, you can try the following: 1) Check the network connectivity between the nodes; 2) Verify the user has the correct permissions to update the cluster state; 3) Check the rollup job configuration for any errors and correct them; 4) Restart the Elasticsearch cluster if necessary.

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 ” failed to publish new cluster state with rollup metadata ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, plugin, cluster.

Log Context

Log “failed to publish new cluster state with rollup metadata” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public void onFailure(Exception e) {
 new ElasticsearchException("failed to publish new cluster state with rollup metadata"; e)
 }; newExecutor());


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?