# If you can't delete a "stuck" (In progress/aborted) snapshot **URL:** \ **Category:** Elasticsearch\ **Created:** [November 4, 2016, 6:24pm UTC](https://discuss.elastic.co/t/if-you-cant-delete-a-stuck-in-progress-aborted-snapshot/65041 "2016-11-04T18:24:31Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![casieowen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casieowen/32/8734_2.png) [@casieowen](https://discuss.elastic.co/u/casieowen)\ **Post date:** [November 4, 2016, 6:24pm UTC](https://discuss.elastic.co/t/if-you-cant-delete-a-stuck-in-progress-aborted-snapshot/65041/1 "2016-11-04T18:24:31Z")
Maybe this is only an issue in older versions, but I've seen a few posts about this and no solution other than rolling restarts. I've seen this issue a few times, and have been able to resolve it without restarting all the nodes. You can tun GET /\_snapshot/backup/\_status to get the details of the snapshot that is stuck in progress, then search the output for "stage": "INIT". In each case, I found a shard in initializing (INIT) stage for one of the indices in the stuck snapshot. You'll see something like: "your\_index" "3": { "stage": "INIT", "stats": { "number\_of\_files": 0, "processed\_files": 0, "total\_size\_in\_bytes": 0, "processed\_size\_in\_bytes": 0, "start\_time\_in\_millis": 1478143477100, "time\_in\_millis": 0 }, "node": "somenonfriendlyid" You can then run Get \_nodes/stats to get the friendly name associated to that node value, and then restart only that node. That has worked twice for me. ---
**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:06pm UTC](https://discuss.elastic.co/t/if-you-cant-delete-a-stuck-in-progress-aborted-snapshot/65041/2 "2017-07-05T22:06:27Z")