Log Cluster state update task took above the warn threshold of – How To Solve Related Issues

Log Cluster state update task took above the warn threshold of – How To Solve Related Issues

Opster Team

April-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)


This guide will help you check for common problems that cause the log “Cluster state update task took above the warn threshold of” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, master, task, threshold.

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 discover the cause of many errors and provides suitable actionable recommendations. 


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 MasterService.java
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 {


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Lots Of Cluster State Update Task Z  

Timetaken By A Cluster State Update  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now