---
title: High Cluster Pending Tasks
description: Describes what AutoOps detects and surfaces with the High Cluster Pending Tasks insight: A large backlog of cluster management tasks is waiting to run.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/high_cluster_pending_tasks
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# High Cluster Pending Tasks
A large backlog of cluster management tasks is waiting to run. That means the cluster cannot apply metadata changes fast enough for current load.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value                       |
|-----------|-----------------------------|
| Component | Elasticsearch               |
| Severity  | High                        |
| Scope     | Cluster                     |
| Domains   | performance, cluster-health |


## Customization settings

You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to [AutoOps event settings](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/monitor/autoops/ec-autoops-event-settings) for details.
The default customization settings are:

| Setting                                      | Type    | Default |
|----------------------------------------------|---------|---------|
| Cluster pending tasks threshold              | Integer | 500     |
| Consecutive samples required above threshold | Integer | 6       |

<tip>
  Raising these thresholds reduces noise but delays detection. Lowering them triggers the insight sooner but can increase alerts during minor blips.
</tip>


## Example: What you might see in AutoOps

The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.

### Cluster pending tasks have been elevated for over 5 consecutive samplings


#### What was detected

There are currently 12 pending tasks in the cluster management queue, sustained for over 5 consecutive samplings.

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="Review pending cluster tasks">
  **Condition**: Always shown for this insight.Review pending cluster tasks to see what the master is waiting on. Use the action below to call the pending tasks API.
  ```json
  ```

  <note>
    Requires the `manage cluster` privilege. Requires Elasticsearch 8.0.0 or later. This action is read-only.
  </note>
</dropdown>


#### Background and impact

When a cluster has too many pending tasks sustained over multiple samplings, it’s a sign that the cluster cannot keep up with its current load and the cause of delay should be investigated. Pending tasks can be monitored using the pending cluster tasks API which returns a list of cluster state changes that haven't been executed yet.