# Elastic Cloud AWS: Storage Size Drops after Reboot of entire cluster

**URL:** <https://discuss.elastic.co/t/elastic-cloud-aws-storage-size-drops-after-reboot-of-entire-cluster/165383>\
**Category:** Elasticsearch\
**Created:** [January 23, 2019, 10:49am UTC](https://discuss.elastic.co/t/elastic-cloud-aws-storage-size-drops-after-reboot-of-entire-cluster/165383 "2019-01-23T10:49:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![matthew.whill](https://avatars.discourse-cdn.com/v4/letter/m/dc4da7/32.png) [@matthew.whill](https://discuss.elastic.co/u/matthew.whill)\
**Post date:** [January 23, 2019, 10:49am UTC](https://discuss.elastic.co/t/elastic-cloud-aws-storage-size-drops-after-reboot-of-entire-cluster/165383/1 "2019-01-23T10:49:20Z")

</div>

I am running an instance of Elastic Cloud via the offered AWS facility.  
I am saving a large amount of documents to the cluster and starting to reach the max capacity for storage.

When I reach a certain point the indexes will go into READ ONLY mode (which is expected). However, out of curiosity I do a "Full restart. All instances restart simultaneously." When they restart, a significant amount of space becomes available and the indexes are no longer read only.

The document counts in the indexes do not change.

So why does a full restart clear space in the storage?

I dont know if it makes any difference, but I have "index.refresh\_interval": "-1" on all my indexes.

Thanks,  
Matt

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 23, 2019, 11:31am UTC](https://discuss.elastic.co/t/elastic-cloud-aws-storage-size-drops-after-reboot-of-entire-cluster/165383/2 "2019-01-23T11:31:31Z")

</div>

It would be useful to compare the outputs of `GET /_cat/segments` before and after the restart, and to do a similar comparison of `GET /_stats?level=shards`. While a node is running, some data is kept in multiple places (the translog, and potentially also in more than one segment) but when a node shuts down cleanly it performs a [flush](https://www.elastic.co/guide/en/elasticsearch/reference/6.5/indices-flush.html) which might mean it can discard some of these copies. The API calls above will give a much more detailed picture.

---

<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 20, 2019, 11:31am UTC](https://discuss.elastic.co/t/elastic-cloud-aws-storage-size-drops-after-reboot-of-entire-cluster/165383/3 "2019-02-20T11:31:43Z")

</div>

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