elasticsearch resource_error ai_generated true

SnapshotInProgressException: snapshot [my_repo:snapshot_2025] is already in progress, cannot start new snapshot until current one completes or is cancelled

ID: elasticsearch/snapshot-in-progress-timeout

Also available as: JSON · Markdown · 中文
90%Fix Rate
90%Confidence
1Evidence
2024-06-10First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
7.10.0 active — — —
7.17.0 active — — —
8.0.0 active — — —

Root Cause

A concurrent snapshot creation was attempted while another snapshot is still running in the same repository, which is not allowed.

generic

中文

在同一个仓库中另一个快照仍在运行时尝试并发创建快照，这是不允许的。

Official Documentation

https://www.elastic.co/guide/en/elasticsearch/reference/7.17/snapshot-restore.html

Workarounds

  1. 95% success Cancel the ongoing snapshot: `POST _snapshot/my_repo/snapshot_2025/_cancel` then wait for completion before starting a new one. 
    Cancel the ongoing snapshot: `POST _snapshot/my_repo/snapshot_2025/_cancel` then wait for completion before starting a new one.
  2. 85% success If cancellation fails, delete the snapshot: `DELETE _snapshot/my_repo/snapshot_2025` (only if it is stuck and no data is needed). 
    If cancellation fails, delete the snapshot: `DELETE _snapshot/my_repo/snapshot_2025` (only if it is stuck and no data is needed).

中文步骤

  1. Cancel the ongoing snapshot: `POST _snapshot/my_repo/snapshot_2025/_cancel` then wait for completion before starting a new one.
  2. If cancellation fails, delete the snapshot: `DELETE _snapshot/my_repo/snapshot_2025` (only if it is stuck and no data is needed).

Dead Ends

Common approaches that don't work:

  1. 95% fail

    The error is not a timeout issue but a concurrency conflict; timeout settings do not prevent concurrent snapshots.

  2. 80% fail

    Restarting may cause data loss or corruption; the snapshot lock is stored in the cluster state and may persist after restart.