High cluster pending tasks
A large backlog of cluster management tasks is waiting to run. The cluster cannot apply metadata changes fast enough for current load.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | High |
| Scope | Cluster |
| Domains | performance, cluster-health |
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 |
|---|---|---|
| Cluster pending tasks threshold | Integer | 500 |
| Consecutive samples required above threshold | Integer | 6 |
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.
There are 12 pending tasks in the cluster management queue, sustained for over 5 consecutive samplings.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
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.
GET _cluster/pending_tasks
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action is read-only.
When the cluster management queue grows faster than the elected master can apply changes, pending tasks accumulate. Each task represents a cluster-state update that has not yet been executed. Sustained high pending task counts often signal rapid cluster-state churn or a master that cannot keep pace with current load. Metadata changes can lag until the backlog clears.