Management queue size
The management queue has grown large on one or more nodes, so cluster-state and administrative tasks are waiting to run. A deep queue can delay shard allocation, settings changes, and other cluster management work.
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 |
|---|---|---|
| Management queue threshold | Integer | 5 |
| Consecutive samples above threshold | Integer | 3 |
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 management queue is elevated on es-data-01 and es-data-02.
Total tasks in the management queue: 128
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
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.
GET _cat/pending_tasks?v
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action is read-only.
The management queue holds cluster tasks that cannot run immediately. When it backs up, either too many tasks are being submitted or something is blocking task execution.
If the queue stays high, cluster changes slow down. In severe cases, delayed allocation can contribute to instability or a red cluster status when shards cannot be assigned.