Long running delete by query task
Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECH
Generally available
ECK
Generally available
ECE
Generally available
Self-managed
Generally available
A delete-by-query task has exceeded your configured runtime threshold. Delete by query scrolls matching documents and removes them in batches, keeping search contexts open for extended periods.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Node |
| Domains | performance, indexing, stability, tasks |
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 |
|---|---|---|
| Long running delete by query task threshold in minutes | Integer | 60 |
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 3 tasks that ran more than the 12 minutes threshold.
The longest task running start time was 2026-03-15T14:22:00 UTC time.
The longest task running time is 48 minutes.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Improve long delete-by-query tasks
Condition: Shown when delete-by-query tasks are not cancellable.
Use slicing to parallelize the task, narrow the query with filters to match fewer documents, and temporarily raise or turn off the refresh interval during the run. Review index mappings and analysis for optimization opportunities.
Delete by query removes documents that match a query by scrolling the index and deleting matched documents in batches. The scroll context stays in memory until the task completes, and each batch refreshes the keep-alive timeout, so deletes on large indices can run for a long time.
Broad queries that match many documents, tombstone accumulation during concurrent indexing, and several delete-by-query tasks running together increase heap pressure and I/O on data nodes. Extended deletes during heavy ingest or search traffic can slow cluster operations on affected nodes.