Cluster state update task took above the warn threshold of – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when an Elasticsearch cluster state update task takes longer than the set warning threshold. This could be due to heavy indexing, large data volumes, or insufficient resources. To resolve this, you can optimize your indexing process, reduce the size of your data by deleting unnecessary indices, or increase your cluster resources. Additionally, consider adjusting the warn threshold if it’s set too low for your use case.

We recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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).


It’s quite essential to understand what Cluster state is and why Elasticsearch makes sure to log a warning if the time taken to update it extends beyond the default threshold of 10 seconds.

The Cluster state consists of the information of all nodes and shards in the cluster and all of the cluster and index level settings.

Cluster state is computed on the master node and published to all nodes in the cluster and is very important for the functioning of the Elasticsearch cluster. 

This is why Elasticsearch throws a warning if it’s not able to compute and publish these changes to all the nodes within threshold.

Potential causes and a detailed guide on how to solve and code fragments from Elasticsearch are covered by an Opster ES expert in this STOF answer.

Log Context

Log “cluster state update task [{}] took [{}] above the warn threshold of {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    protected void warnAboutSlowTaskIfNeeded(TimeValue executionTime; String source) {
        if (executionTime.getMillis() > slowTaskLoggingThreshold.getMillis()) {
            logger.warn("cluster state update task [{}] took [{}] above the warn threshold of {}"; source; executionTime;

    private static class DelegatingAckListener implements Discovery.AckListener {


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?