# Snapshot stuck IN\_PROGRESS

**URL:** <https://discuss.elastic.co/t/snapshot-stuck-in-progress/148552>\
**Category:** Elasticsearch\
**Created:** [September 14, 2018, 4:19am UTC](https://discuss.elastic.co/t/snapshot-stuck-in-progress/148552 "2018-09-14T04:19:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![markuchi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markuchi/32/35534_2.png) [@markuchi](https://discuss.elastic.co/u/markuchi)\
**Post date:** [September 14, 2018, 4:19am UTC](https://discuss.elastic.co/t/snapshot-stuck-in-progress/148552/1 "2018-09-14T04:19:45Z")

</div>

Running a snapshot has taken days and has been IN\_PROGRESS state

During the snapshot we hit the low watermark and want to stop the snapshot and redo one we fix the watermark.

We have performed rolling restarts multiple times as well as try and delete the snapshots.  
Deleting snapshots just hang and keep going to more than 24 hours.

"state" : "IN\_PROGRESS",  
"start\_time" : "2018-09-11T22:00:21.694Z",  
"start\_time\_in\_millis" : 1536703221694,  
"end\_time" : "1970-01-01T00:00:00.000Z",  
"end\_time\_in\_millis" : 0,  
"duration\_in\_millis" : -1536703221694,  
"failures" : [],  
"shards" : {  
"total" : 0,  
"failed" : 0,  
"successful" : 0

running \_status on the snapshot shows some FAILURE:

"shards" : {  
"0" : {  
"stage" : "FAILURE",  
"stats" : {  
"number\_of\_files" : 0,  
"processed\_files" : 0,  
"total\_size\_in\_bytes" : 0,  
"processed\_size\_in\_bytes" : 0,  
"start\_time\_in\_millis" : 0,  
"time\_in\_millis" : 0  
}  
},

### Specifications

- Version: Curator 5.5.4, ElasticSearch 5.6.10
- Platform: CentOS 7

Any assistance will be appreciated.

---

<div class="post-metadata">

**Author:** ![markuchi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markuchi/32/35534_2.png) [@markuchi](https://discuss.elastic.co/u/markuchi)\
**Post date:** [September 17, 2018, 3:45am UTC](https://discuss.elastic.co/t/snapshot-stuck-in-progress/148552/2 "2018-09-17T03:45:05Z")

</div>

bump

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [September 17, 2018, 4:06am UTC](https://discuss.elastic.co/t/snapshot-stuck-in-progress/148552/3 "2018-09-17T04:06:24Z")

</div>

I changed the title. Curator is a red herring here, and it may turn away potential help.

---

<div class="post-metadata">

**Author:** ![markuchi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markuchi/32/35534_2.png) [@markuchi](https://discuss.elastic.co/u/markuchi)\
**Post date:** [September 17, 2018, 4:50am UTC](https://discuss.elastic.co/t/snapshot-stuck-in-progress/148552/4 "2018-09-17T04:50:05Z")

</div>

Thanks.  
I finally fixed the issue.

I tried closing indexes and found that there were a few that wouldn't close.  
I did a rolling restart but they still wouldn't close.  
I then restarted all servers in the cluster at the same time and the indexes finally closed.  
Snapshot was still running even after this.  
Reopened all the closed indexes and the snapshot was finally no longer running.

Running a snapshot now completes.

---

<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:** [October 15, 2018, 4:50am UTC](https://discuss.elastic.co/t/snapshot-stuck-in-progress/148552/5 "2018-10-15T04:50:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.