# Running Elastic Local in Cluster Mode

**URL:** <https://discuss.elastic.co/t/running-elastic-local-in-cluster-mode/66825>\
**Category:** Elasticsearch\
**Created:** [November 22, 2016, 8:22am UTC](https://discuss.elastic.co/t/running-elastic-local-in-cluster-mode/66825 "2016-11-22T08:22:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mainec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mainec/32/5557_2.png) [@mainec](https://discuss.elastic.co/u/mainec)\
**Post date:** [November 22, 2016, 11:29am UTC](https://discuss.elastic.co/t/running-elastic-local-in-cluster-mode/66825/2 "2016-11-22T11:29:22Z")

</div>

You might want to check out this previous post:

> [@Can I run multiple Elasticsearch nodes on the same machine?](https://discuss.elastic.co/t/can-i-run-multiple-elasticsearch-nodes-on-the-same-machine/67):
>
> We generally recommend scaling horizontally by adding small/medium machines. But we do have a few customers with big machines (eg. 512 RAM, 256 cores, etc..) who have deployed multiple Elasticsearch nodes per big machine. There are some caveats and recommendations if you choose this deployment architecture: Max heap size for each node instance should be \< 32Gb. This is because a heap size above 32Gb will actually be counterproductive for the JVM will stop compressing pointers ([https://wikis…](https://wikis.oracle.com/display/HotSpotInternals/CompressedOops)

---

_[View the full topic](https://discuss.elastic.co/t/running-elastic-local-in-cluster-mode/66825)._