# One node in cluster is using (a lot) more heap space and cpu

**URL:** <https://discuss.elastic.co/t/one-node-in-cluster-is-using-a-lot-more-heap-space-and-cpu/29429>\
**Category:** Elasticsearch\
**Created:** [September 16, 2015, 5:17pm UTC](https://discuss.elastic.co/t/one-node-in-cluster-is-using-a-lot-more-heap-space-and-cpu/29429 "2015-09-16T17:17:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![klahnakoski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/klahnakoski/32/3679_2.png) [@klahnakoski](https://discuss.elastic.co/u/klahnakoski)\
**Post date:** [September 16, 2015, 6:02pm UTC](https://discuss.elastic.co/t/one-node-in-cluster-is-using-a-lot-more-heap-space-and-cpu/29429/3 "2015-09-16T18:02:10Z")

</div>

I have seen this happen during bulk loading[1]: One node has the majority of primary shards, and will crash as a result

[1] [Reducing Memory Consuption while Bulk Indexing](https://discuss.elastic.co/t/reducing-memory-consuption-while-bulk-indexing/26447)

---

_[View the full topic](https://discuss.elastic.co/t/one-node-in-cluster-is-using-a-lot-more-heap-space-and-cpu/29429)._