# Large heap usage with each node

**URL:** <https://discuss.elastic.co/t/large-heap-usage-with-each-node/969>\
**Category:** Elasticsearch\
**Created:** [May 20, 2015, 2:22pm UTC](https://discuss.elastic.co/t/large-heap-usage-with-each-node/969 "2015-05-20T14:22:57Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\
**Post date:** [May 20, 2015, 11:25pm UTC](https://discuss.elastic.co/t/large-heap-usage-with-each-node/969/8 "2015-05-20T23:25:52Z")

</div>

It's actually 48 indices with 32 shards each. So there 3142 shards including the replicas... I'm doing index per day strategy.

We expect to grow 150% next year so I would expect the cluster to grow to a dozen pysical nodes maybe more.

So 150% of 2.5-3 billion documemts. So I'm now I'm trying to test with 2.5 billion, but expect that to grow next year by 150%.

At 800 million docs I lost the cluster because there was way to many pauses and no collections hapening so it kept trying to recover over and over. So I restarted re-indexing and reached 380 million. So now checking options...

---

_[View the full topic](https://discuss.elastic.co/t/large-heap-usage-with-each-node/969)._
