# Correct usage of Coordinating role node

**URL:** <https://discuss.elastic.co/t/correct-usage-of-coordinating-role-node/109988>\
**Category:** Elasticsearch\
**Created:** [December 1, 2017, 10:34pm UTC](https://discuss.elastic.co/t/correct-usage-of-coordinating-role-node/109988 "2017-12-01T22:34:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 2, 2017, 10:47am UTC](https://discuss.elastic.co/t/correct-usage-of-coordinating-role-node/109988/2 "2017-12-02T10:47:38Z")

</div>

Having 2 master eligible nodes in a cluster is a bad idea. You should always aim to have exactly 3 so two nodes can elect a new master should one fail or leave. I would therefore recommend that you set up 3 equally sized nodes that hold data and are master eligible. In addition to this you can use a coordinating only node with Kibana.

With this setup, you would direct indexing operations at the master/data nodes.

If having 3 data nodes is not an option, I would recommend setting up the cluster with 2 master/data nodes and one smaller dedicated master node. In this configuration you would send all indexing request to one of the master/data nodes. In addition to this you can use a coordinating only node with Kibana.

---

_[View the full topic](https://discuss.elastic.co/t/correct-usage-of-coordinating-role-node/109988)._