Loading

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.

Field Value
Component Elasticsearch
Severity Low
Scope Node
Domains performance, cluster-health, stability

You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to 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.

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 total number of tasks in management queue: 128.

The affected node/s are: es-data-01 and es-data-02

Note

AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.

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.