# 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:** 1\
**Showing post:** 2

<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…

---

_[View the full topic](https://discuss.elastic.co/t/max-suggested-index-sizes-document-amount-etc/347937)._
