# Hardware Guidelines for Coordinating Node

**URL:** <https://discuss.elastic.co/t/hardware-guidelines-for-coordinating-node/106760>\
**Category:** Elasticsearch\
**Created:** [November 7, 2017, 9:31pm UTC](https://discuss.elastic.co/t/hardware-guidelines-for-coordinating-node/106760 "2017-11-07T21:31:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![grantcurell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grantcurell/32/23813_2.png) [@grantcurell](https://discuss.elastic.co/u/grantcurell)\
**Post date:** [November 7, 2017, 9:31pm UTC](https://discuss.elastic.co/t/hardware-guidelines-for-coordinating-node/106760/1 "2017-11-07T21:31:42Z")

</div>

With regards to coordinating nodes as described here: [How to use a load balancer with Elasticsearch?](https://discuss.elastic.co/t/how-to-use-a-load-balancer-with-elasticsearch/72)

What is the recommended resource allocation? Obviously that varies a lot dependent on a huge number of factors, but there are ballpark estimations for the other types of node (4 gigs of RAM a core etc).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 7, 2017, 10:01pm UTC](https://discuss.elastic.co/t/hardware-guidelines-for-coordinating-node/106760/2 "2017-11-07T22:01:32Z")

</div>

Start with 4GB RAM, 2-4 cores.  
You don't need much disk space, just enough for the OS and install.  
You can run \>50% heap for these, as there is no off heap file caching that Elasticsearch would leverage. I wouldn't go \>75% though.

---

<div class="post-metadata">

**Author:** ![grantcurell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grantcurell/32/23813_2.png) [@grantcurell](https://discuss.elastic.co/u/grantcurell)\
**Post date:** [November 9, 2017, 7:23pm UTC](https://discuss.elastic.co/t/hardware-guidelines-for-coordinating-node/106760/3 "2017-11-09T19:23:44Z")

</div>

So would it be sane to do something like have 3 designated data nodes with a designated master / coordinating node sitting in front of them?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 9, 2017, 7:27pm UTC](https://discuss.elastic.co/t/hardware-guidelines-for-coordinating-node/106760/4 "2017-11-09T19:27:36Z")

</div>

No, see [https://www.elastic.co/guide/en/elasticsearch/guide/2.x/important-configuration-changes.html#\_minimum\_master\_nodes](https://www.elastic.co/guide/en/elasticsearch/guide/2.x/important-configuration-changes.html#_minimum_master_nodes)

---

<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 7, 2017, 7:28pm UTC](https://discuss.elastic.co/t/hardware-guidelines-for-coordinating-node/106760/5 "2017-12-07T19:28:01Z")

</div>

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