---
title: Management Queue Size
description: Describes what AutoOps detects and surfaces with the Management Queue Size insight: The cluster management queue has grown large on one or more nodes, meaning many cluster-state tasks are waiting to run.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/management_queue_size
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
---

# Management Queue Size
The cluster management queue has grown large on one or more nodes, meaning many cluster-state tasks are waiting to run. A deep queue can delay shard allocation, settings changes, and other administrative work.
<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  | Low                                    |
| Scope     | Node                                   |
| Domains   | performance, cluster-health, stability |


## 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 |
|------------------------------------------|---------|---------|
| High management queue activity threshold | Integer | 5       |
| Successive samplings to trigger          | Integer | 3       |

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

### The management queue size is high on the following node/s: `es-data-01`


#### What was detected

The total number of tasks in management queue: 128.
The affected node/s are: `es-data-01` and `es-data-02`

#### 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.The management queue on `es-data-01` is high. Check cluster state and logs for excessive activity, then list pending tasks with the action below.
  ```json
  ```

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


#### Background and impact

Impact: A high number of tasks in the management queue can cause cluster instability, potentially leading to data loss and cluster status turning red if shards cannot be allocated.
The management queue is where cluster tasks are queued if they cannot be carried out immediately.
If management tasks start to back up, it’s an indication either that an too many of tasks are being created or that something is keeping the tasks from being carried out properly.