# Questions about loadbalancing kibana to multiple ES nodes

**URL:** <https://discuss.elastic.co/t/questions-about-loadbalancing-kibana-to-multiple-es-nodes/183008>\
**Category:** Kibana\
**Created:** [May 28, 2019, 7:22am UTC](https://discuss.elastic.co/t/questions-about-loadbalancing-kibana-to-multiple-es-nodes/183008 "2019-05-28T07:22:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)\
**Post date:** [May 28, 2019, 7:22am UTC](https://discuss.elastic.co/t/questions-about-loadbalancing-kibana-to-multiple-es-nodes/183008/1 "2019-05-28T07:22:59Z")

</div>

Hi,

I am currently setting up my first multi node cluster of the stack.

How do I configure kibana correctly to loadbalance over the ES nodes?

In Kibana config I have the key elasticsearch.hosts.  
Do I understand correctly kibana will distribute it's requests over all nodes if I place all cluster nodes here?  
What if an additional node joins, does it need to be configured here too, or will kibana only need one available ES node and fetches cluster information (which nodes are available) from there?  
Is it mandatory to list all nodes to get complete data or would 1 available ES node be enough?

I found this doc here:  
[https://www.elastic.co/guide/en/kibana/current/production.html#load-balancing](https://www.elastic.co/guide/en/kibana/current/production.html#load-balancing)

Where exactly is the benefit of running coordinating-only-nodes? Is it only to free up the coordinating resources from the other nodes or is it because the coordinating only node will discover all ES nodes automatically to loadbalance while kibana needs to be configured manually?

Thanks, Andreas

---

<div class="post-metadata">

**Author:** ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)\
**Post date:** [May 28, 2019, 11:13am UTC](https://discuss.elastic.co/t/questions-about-loadbalancing-kibana-to-multiple-es-nodes/183008/2 "2019-05-28T11:13:33Z")

</div>

Hey @asp,

The Coordinating-Only Node is effectively a load-balancer to multiple ES nodes. It is also responsible, as you noted, for offloading the creation of the final result set (see [https://www.elastic.co/guide/en/elasticsearch/reference/7.1/modules-node.html#coordinating-node](https://www.elastic.co/guide/en/elasticsearch/reference/7.1/modules-node.html#coordinating-node)).

The benefit of having multiple ES nodes specified in your `kibana.yml` is for high availability. If you only have the single Coordinating Node specified, then Kibana will only function if that specific node is available. If that node falls out of the cluster, then Kibana will not be usable. Specifying multiple nodes here protects you from that scenario.

---

<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:** [June 25, 2019, 11:13am UTC](https://discuss.elastic.co/t/questions-about-loadbalancing-kibana-to-multiple-es-nodes/183008/3 "2019-06-25T11:13:35Z")

</div>

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