# Kibana with Multinode Elasticsearch cluster

**URL:** <https://discuss.elastic.co/t/kibana-with-multinode-elasticsearch-cluster/75337>\
**Category:** Kibana\
**Created:** [February 16, 2017, 1:42pm UTC](https://discuss.elastic.co/t/kibana-with-multinode-elasticsearch-cluster/75337 "2017-02-16T13:42:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [February 16, 2017, 4:01pm UTC](https://discuss.elastic.co/t/kibana-with-multinode-elasticsearch-cluster/75337/2 "2017-02-16T16:01:17Z")

</div>

Kibana will make requests to the node at `elasticsearch.url`, and that node may end up talking with other nodes to retrieve data. Running an elasticsearch coordinating node on the same machine([guide](https://www.elastic.co/guide/en/kibana/current/production.html#load-balancing)) is currently recommended for balancing. If that node does goes down then correct, Kibana will go down with it.

Kibana doesn't support talking directly to multiple elasticsearch nodes now, we have an issue for tracking it [here](https://github.com/elastic/kibana/issues/214) that has some suggestions. You could put a load balancer between kibana and elasticsearch, or have multiple instances of Kibana pointing to different nodes with a load balancer in front.

---

_[View the full topic](https://discuss.elastic.co/t/kibana-with-multinode-elasticsearch-cluster/75337)._