# ABORTED snapshot blocks doing snapshot

**URL:** <https://discuss.elastic.co/t/aborted-snapshot-blocks-doing-snapshot/17523>\
**Category:** Elasticsearch\
**Created:** [May 15, 2014, 12:15am UTC](https://discuss.elastic.co/t/aborted-snapshot-blocks-doing-snapshot/17523 "2014-05-15T00:15:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeffz](https://avatars.discourse-cdn.com/v4/letter/j/e9c0ed/32.png) [@Jeffz](https://discuss.elastic.co/u/Jeffz)\
**Post date:** [May 15, 2014, 12:15am UTC](https://discuss.elastic.co/t/aborted-snapshot-blocks-doing-snapshot/17523/1 "2014-05-15T00:15:55Z")

</div>

Our Elasticsearch cluster has an aborted snapshot. Here is what I got by calling 'curl \_cluster/state', see the content below. It has been in this state for days.

```
 "snapshots": {
     "snapshots": [
        {
           "repository": "searchbackup",
           "snapshot": "backup140509",
           "include_global_state": true,
           "state": "ABORTED",
           "indices": [
              "A-v1",
              "B-v1",
              "C-v1",
              "D-v1"
           ]

```

The problem with this is that it didn't allow us to do the snapshot any more, and returned the following error message : "ConcurrentSnapshotExecutionException a snapshot is already running". We tried to delete the aborted snapshot as documented at [Snapshot And Restore](http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html) but it didn't work.

Is there a way that we could clean up this aborted snapshot and re-enable the snapshot for our cluster?

---

<div class="post-metadata">

**Author:** ![Preeti\_Raj\_Buchhada](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/preeti_raj_buchhada/32/8971_2.png) [@Preeti\_Raj\_Buchhada](https://discuss.elastic.co/u/Preeti_Raj_Buchhada)\
**Post date:** [June 20, 2016, 5:27am UTC](https://discuss.elastic.co/t/aborted-snapshot-blocks-doing-snapshot/17523/2 "2016-06-20T05:27:41Z")

</div>

Hi, we are facing the exact same issue. How did you overcome it (if at all) ?

---

<div class="post-metadata">

**Author:** ![Preeti\_Raj\_Buchhada](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/preeti_raj_buchhada/32/8971_2.png) [@Preeti\_Raj\_Buchhada](https://discuss.elastic.co/u/Preeti_Raj_Buchhada)\
**Post date:** [June 20, 2016, 6:49am UTC](https://discuss.elastic.co/t/aborted-snapshot-blocks-doing-snapshot/17523/3 "2016-06-20T06:49:01Z")

</div>

Rolling restart as suggested in [Snapshot operation stuck IN\_PROGRESS, delete command doesn't work](https://discuss.elastic.co/t/snapshot-operation-stuck-in-progress-delete-command-doesnt-work/36951) solved it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:42pm UTC](https://discuss.elastic.co/t/aborted-snapshot-blocks-doing-snapshot/17523/4 "2017-07-05T22:42:26Z")

</div>