# Elastic clound 100% memory on instances, snapshot is stuck in IN\_PROGRESS

**URL:** <https://discuss.elastic.co/t/elastic-clound-100-memory-on-instances-snapshot-is-stuck-in-in-progress/260439>\
**Category:** Elasticsearch\
**Created:** [January 7, 2021, 1:12pm UTC](https://discuss.elastic.co/t/elastic-clound-100-memory-on-instances-snapshot-is-stuck-in-in-progress/260439 "2021-01-07T13:12:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![birdy1980](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/birdy1980/32/80409_2.png) [@birdy1980](https://discuss.elastic.co/u/birdy1980)\
**Post date:** [January 7, 2021, 1:12pm UTC](https://discuss.elastic.co/t/elastic-clound-100-memory-on-instances-snapshot-is-stuck-in-in-progress/260439/1 "2021-01-07T13:12:08Z")

</div>

Hello,

On one of our cloud deployments we have a bit of a problem. The memory usage grew to 100%. It is a high availability cluster in 2 zones, with a third instance as tiebreaker.

We want to upgrade the instance to have more memory. I have noticed that during such an upgrade a snapshot is made. At the moment no snapshots are made because the last one is stuck in IN\_PROGRESS. It never completes at the moment. Also kibana is not working correctly. Lot of "out of memory" errors

I'm reluctant to start the upgrade process because the snapshot is stuck in IN\_PROGRESS.

What would be wise to do now? First try a restart of the cluster maybe?

With regards, Ben

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 11, 2021, 12:26am UTC](https://discuss.elastic.co/t/elastic-clound-100-memory-on-instances-snapshot-is-stuck-in-in-progress/260439/2 "2021-01-11T00:26:31Z")

</div>

I would suggest you reach out to the Support team for assistance with this one 🙂

---

<div class="post-metadata">

**Author:** ![birdy1980](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/birdy1980/32/80409_2.png) [@birdy1980](https://discuss.elastic.co/u/birdy1980)\
**Post date:** [January 11, 2021, 7:52am UTC](https://discuss.elastic.co/t/elastic-clound-100-memory-on-instances-snapshot-is-stuck-in-in-progress/260439/3 "2021-01-11T07:52:16Z")

</div>

Thank you, The issue has been resoved.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 11, 2021, 7:52am UTC](https://discuss.elastic.co/t/elastic-clound-100-memory-on-instances-snapshot-is-stuck-in-in-progress/260439/4 "2021-01-11T07:52:37Z")

</div>

Can you share any info on what the problem and solution was?

---

<div class="post-metadata">

**Author:** ![birdy1980](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/birdy1980/32/80409_2.png) [@birdy1980](https://discuss.elastic.co/u/birdy1980)\
**Post date:** [January 11, 2021, 12:00pm UTC](https://discuss.elastic.co/t/elastic-clound-100-memory-on-instances-snapshot-is-stuck-in-in-progress/260439/5 "2021-01-11T12:00:27Z")

</div>

First we tried to restart the cluster, that failed to complete. Then we tried to upgrade, and there was an option to skip the snapshot. The upgrade was completed successful.

---

<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:** [February 8, 2021, 12:00pm UTC](https://discuss.elastic.co/t/elastic-clound-100-memory-on-instances-snapshot-is-stuck-in-in-progress/260439/6 "2021-02-08T12:00:31Z")

</div>

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