Long running snapshot task
A snapshot task is taking longer than your configured threshold to finish. Snapshots read shard data and stream it to the repository, so large indices, resource contention, or slow repository connectivity extend duration.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Node |
| Domains | performance, snapshots-backup, 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 snapshot 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.
Cancel long-running tasks
Condition: Shown when cancellable.
Cancel long-running tasks (es-data-01:4521, es-data-02:7788) that are affecting cluster stability. Use the action below.
POST _tasks/es-data-01:4521, es-data-02:7788/_cancel
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
Fix non-cancellable snapshot tasks
Condition: Shown when not cancellable.
Review snapshot tasks that cannot be cancelled. Adjust snapshot schedule, repository performance, or cluster load so snapshots complete or can be retried safely.
Reduce snapshot scope
Condition: Shown when snapshot task is not cancellable.
Create smaller snapshots by targeting fewer indices and taking them more often so long-running snapshot tasks stay cancellable.
Snapshots capture index and cluster metadata and write them to a registered repository. The operation reads data from primary shards and streams it to the repository, so index size, shard count, and repository speed all affect duration.
High cluster load, network latency to the repository, or unassigned or corrupted shards can prolong or stall snapshot work. Extended snapshots tie up resources and increase the risk of incomplete backups.