Long running bulk index task
At least one bulk indexing task has exceeded your configured runtime threshold. Long bulk jobs hold thread pool and heap resources and can contend with other ingest and search work.
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 bulk index task threshold in minutes | Integer | 10 |
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 bulk index tasks
Condition: Shown when bulk index tasks are not cancellable.
Split bulk payloads into smaller batches and limit parallel bulk requests to reduce memory pressure. Temporarily raise or turn off the refresh interval during the run, and review index mappings and analysis for optimization opportunities.
Bulk indexing batches many document operations in one request and is usually more efficient than single-document indexing. Even so, large or long-running bulk tasks consume indexing thread pool capacity, heap for buffering, and disk I/O on the nodes that run them.
Parallel bulk streams, oversized batches, slow ingest pipelines, and undersized nodes commonly extend bulk duration. If bulk tasks run long enough to contend with other work, ingest and search performance on affected nodes can degrade.