# Index size growth

**URL:** <https://discuss.elastic.co/t/index-size-growth/155212>\
**Category:** Elasticsearch\
**Created:** [November 2, 2018, 5:14pm UTC](https://discuss.elastic.co/t/index-size-growth/155212 "2018-11-02T17:14:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![fionamacd](https://avatars.discourse-cdn.com/v4/letter/f/6a8cbe/32.png) [@fionamacd](https://discuss.elastic.co/u/fionamacd)\
**Post date:** [November 2, 2018, 5:14pm UTC](https://discuss.elastic.co/t/index-size-growth/155212/1 "2018-11-02T17:14:46Z")

</div>

I am trying to figure out how best to plan for disk space/EBS volume size for AWS ES.

When I get the weekly index details back like this:

> |green|open|filebeat-test-2018.42|hpJXziswRh-iGY1FOZnqNw|5|1|1309774|0|2.3gb|1.1gb  
> |green|open|filebeat-test-2018.43|zV5NVuiaTA2IotJlervl7Q|5|1|56541495|0|50.4gb|25.2gb  
> |green|open|filebeat-test-2018.44|EH6i4OhDQi-bOtw1ctGxYA|5|1|187165913|0|168.2gb|84.1gb

Does this mean week .44 has 2.3GB + 25.2GB + new 116GB = for total 168GB?  
So weekly data growth for this index is 2GB, then 48GB and then 116GB?

I am trying to understand because I have another index where week .43 is less than the other 2 weeks and I don't understand how that could be!

Fiona

---

<div class="post-metadata">

**Author:** ![gbrown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gbrown/32/34482_2.png) [@gbrown](https://discuss.elastic.co/u/gbrown)\
**Post date:** [November 2, 2018, 10:53pm UTC](https://discuss.elastic.co/t/index-size-growth/155212/2 "2018-11-02T22:53:48Z")

</div>

Each row is a separate index, and each index's size here reflects **only** the data in that week, not a cumulative sum.

You have three indices:

1. `filebeat-test-2018.42` that has approximately 1.1gb of data with one replica, for a total of 2.3gb in that index.
2. `filebeat-test-2018.32` that has approximately 25.2gb of data with one replica, for a total of 50.4gb in that index.
3. `filebeat-test-2018.43` that has approximately 84.1gb of data with one replica, for a total of 168.2gb in that index.

So the total amount of storage being consumed on this by these three indices, is 2.3gb + 50.4gb + 168.2gb = **220.9gb**.

The size of each index just depends on how much log data was produced that week.

Does that help at all?

As an aside, I recommend Elastic's [Elasticsearch Service](https://www.elastic.co/cloud/elasticsearch-service) for running Elasticsearch in AWS .

---

<div class="post-metadata">

**Author:** ![fionamacd](https://avatars.discourse-cdn.com/v4/letter/f/6a8cbe/32.png) [@fionamacd](https://discuss.elastic.co/u/fionamacd)\
**Post date:** [November 5, 2018, 4:14pm UTC](https://discuss.elastic.co/t/index-size-growth/155212/3 "2018-11-05T16:14:28Z")

</div>

Yes, this was very helpful Gordon, thanks for the clarification!

---

<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:** [December 3, 2018, 4:14pm UTC](https://discuss.elastic.co/t/index-size-growth/155212/4 "2018-12-03T16:14:30Z")

</div>

Closed on December 3, 2018, 4:14pm UTC

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