Cluster state update task took above the warn threshold of – How to solve related issues

Cluster state update task took above the warn threshold of – How to solve related issues

Opster Team

43941, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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 and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Overview

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;
                slowTaskLoggingThreshold);
        }
    }

    private static class DelegatingAckListener implements Discovery.AckListener {




 

Run the Check-Up to get customized recommendations like this:

error

The high disk watermark threshold is about to be reached in specific nodes

error-img

Description

There are various “watermark” thresholds on each Elasticsearch cluster. When the high disk watermark threshold has been exceeded, it means disk space is running out. The node will…

error-img

Recommendations

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized code snippet to resolve the issue]

Optimize Elasticsearch Performance

Run The Tool