# Disk space measure for Elasticsearch service

**URL:** <https://discuss.elastic.co/t/disk-space-measure-for-elasticsearch-service/349076>\
**Category:** Elasticsearch\
**Created:** [December 11, 2023, 5:07pm UTC](https://discuss.elastic.co/t/disk-space-measure-for-elasticsearch-service/349076 "2023-12-11T17:07:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaushalshriyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaushalshriyan/32/44563_2.png) [@kaushalshriyan](https://discuss.elastic.co/u/kaushalshriyan)\
**Post date:** [December 11, 2023, 5:07pm UTC](https://discuss.elastic.co/t/disk-space-measure-for-elasticsearch-service/349076/1 "2023-12-11T17:07:34Z")

</div>

Hi,

I have provisioned 300 GB of Hard disk storage to Elastic search stack. Is there a way to measure how much storage is consumed by ES service, as I need to work on Capacity planning. For example, how much memory and storage to be provided to ES service? I am pushing all the application logs to Elastic Stack. How many logs data can be stored in Elasticsearch service for a 300 GB of Hard disk storage?

Please guide me. Thanks in advance.

Best Regards,

Kaushal

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [December 12, 2023, 12:11am UTC](https://discuss.elastic.co/t/disk-space-measure-for-elasticsearch-service/349076/2 "2023-12-12T00:11:07Z")

</div>

It's not clear specification for a simple answer. You might have \<300 GB disk for indices because:

- 1000 bytes=1 KB on the physical disk and 1024 bytes=1 KB on the OS level will be ~280 GB
- you may have ES logs, and temp files on the same partition
- will use replica or not
- disk space watermarking
- ES has own system indices

Let's simplify, you have all 300.00 GB only for indices and 1 replica for FT with 1 acceptable node down.

- Disk watermarking (AZ-5 🙂) - 10-15%, don't count below 10%=\> 270 GB
- 1 GB data in logs or pure JSON ready for ES insert is not 1 GB on disk. This is related to the Lucene engine and ES indexing. Also, it's possible to use the compression which give more space and reduce performances, roughly 10% =\>240 GB
- Replica shards minimum is 1 for fault tolerance - 50% =\> 120-125 GB

In total you will have ~120 GB for indices. Not great not terrible © Dyatlov

Plan to use:

- data only on the dedicated disk
- use ILM for data retention, this will give option for fine tuning indices disk space
- replica 0, for acceptable data loss
- compression, deflate where is possible
- snapshots repository on a separated disk
- nodes monitoring

If you like we can provide you with links to read about text above. then go for design.

---

<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:** [January 9, 2024, 12:11am UTC](https://discuss.elastic.co/t/disk-space-measure-for-elasticsearch-service/349076/3 "2024-01-09T00:11:45Z")

</div>

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