# Max suggested index sizes / document amount etc

**URL:** <https://discuss.elastic.co/t/max-suggested-index-sizes-document-amount-etc/347937>\
**Category:** Elasticsearch\
**Created:** [November 24, 2023, 2:44pm UTC](https://discuss.elastic.co/t/max-suggested-index-sizes-document-amount-etc/347937 "2023-11-24T14:44:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![elk1985](https://avatars.discourse-cdn.com/v4/letter/e/58956e/32.png) [@elk1985](https://discuss.elastic.co/u/elk1985)\
**Post date:** [November 24, 2023, 2:44pm UTC](https://discuss.elastic.co/t/max-suggested-index-sizes-document-amount-etc/347937/1 "2023-11-24T14:44:10Z")

</div>

Hello.  
My cluster is reaching 2000 opened shards. I have two data nodes now.  
I don't want to add another data node and scale up the cluster.  
I'm thinking more like changing indexing strategy. Currently logstash is creating 10 indexes per day. Some are 10 GB some 200MB.  
The question is what is reasonable index size or documents amount to retain cluster performance and stability ?  
Regards.

---

<div class="post-metadata">

**Author:** ![sholzhauer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sholzhauer/32/110282_2.png) [@sholzhauer](https://discuss.elastic.co/u/sholzhauer)\
**Post date:** [November 24, 2023, 2:49pm UTC](https://discuss.elastic.co/t/max-suggested-index-sizes-document-amount-etc/347937/2 "2023-11-24T14:49:26Z")

</div>

Hi, i recently answered this discussion on the forum around sizing as well.  
Hope this helps you too, if any other questions arise let us know.

> [@Cluster currently has \[1000\]/\[1000\] maximum normal shards open](https://discuss.elastic.co/t/cluster-currently-has-1000-1000-maximum-normal-shards-open/347719):
>
> Hi, From the title, this is an error I usually encounter with my Elastic Proof Of Concept. The workaround is easy, I simply close and delete some indices from time to time... But now I'm currently deploying Elastic in a Production environment with 3 dedicated master and multiple data hot, warm, cold, kibana and fleet-server nodes. For the moment, I've only deployed Elastic-Agent on the Fleet-server node (with "fleet" as the namespace) and I can see that there is already many Data Streams cre…

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 24, 2023, 2:56pm UTC](https://discuss.elastic.co/t/max-suggested-index-sizes-document-amount-etc/347937/3 "2023-11-24T14:56:57Z")

</div>

If you have logs data and metrics, which tend to be immutable, I would recommend an average shard size between 25GB and 50GB. The index size would depend on the number of primary shards.

---

<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 22, 2023, 2:56pm UTC](https://discuss.elastic.co/t/max-suggested-index-sizes-document-amount-etc/347937/4 "2023-12-22T14:56:59Z")

</div>

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