# Kibana4 and Elasticsearch cluster
**URL:** https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660
**Category:** Kibana
**Created:** [November 16, 2015, 9:57am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660 "2015-11-16T09:57:52Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@Astro-es](https://discuss.elastic.co/u/Astro-es)
#### Post date: [November 16, 2015, 9:57am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/1 "2015-11-16T09:57:52Z")
I am setting up Elasticsearch, Fluentd and Kibana stack. Initially we had only single ES node.
Now we're setting up Elasticsearch cluster with two nodes to provide HA to Kibana. But the Kibana show clsuter health RED(although the failover happens properly) when another node is elected as master.
Error : Unable to connect to Elasticsearch at [http://localhost:9200](http://localhost:9200).
Following this [topic](https://discuss.elastic.co/t/can-i-use-multiple-hosts-of-same-elasticsearch-cluster-in-kibana-4/26546), I tried to setup cluster with client node. But whenever the elaticsearch on local machine is stopped the dashbaord stops and Kibana shows unable to connect to Elasticsearch at [http://localhost:9200](http://localhost:9200)
How to configure Kibana to be functional even the ES on local machine where Kibana is running goes down? The Kibana isn't picking up new master from cluster once failover is happened.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 16, 2015, 10:12am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/2 "2015-11-16T10:12:37Z")
So you have an existing node that has the data, then you setup just a client node and point KB to that?
---
### Author:  [@Astro-es](https://discuss.elastic.co/u/Astro-es)
#### Post date: [November 16, 2015, 10:14am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/3 "2015-11-16T10:14:54Z")
Yes. That's right.
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [November 16, 2015, 12:01pm UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/4 "2015-11-16T12:01:52Z")
I think Kibana's `elasticsearch_url` option is singular, i.e. it needs to be exactly one URL. As you've noticed this creates a single point of failure. To mitigate that you could e.g. use HAproxy to front of two or more ES instances and point Kibana to the HAproxy hostname/port.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 16, 2015, 10:39pm UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/5 "2015-11-16T22:39:38Z")
Thing is if you have a single data node and you shut it down, then the client cannot do anything as it has no data to serve.
So you need to have two, or ideally 3, data nodes.
---
### Author:  [@Astro-es](https://discuss.elastic.co/u/Astro-es)
#### Post date: [November 17, 2015, 4:03am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/6 "2015-11-17T04:03:12Z")
@warkolm
We have two nodes cluster. The node I tried to shut down was the client node. It should have served data from another node in this case.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 17, 2015, 4:09am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/7 "2015-11-17T04:09:20Z")
Then you should refer to @magnusbaeck's post.
---
### Author:  [@Astro-es](https://discuss.elastic.co/u/Astro-es)
#### Post date: [November 17, 2015, 4:14am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/8 "2015-11-17T04:14:35Z")
@warkolm,
Could you please give me the exact link to the post related to my topic?
Looks like there are multiple posts on this link.
Thanks
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 17, 2015, 4:17am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/9 "2015-11-17T04:17:56Z")
> [@Kibana4 and Elasticsearch cluster](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/4):
>
> I think Kibana's elasticsearch\_url option is singular, i.e. it needs to be exactly one URL. As you've noticed this creates a single point of failure. To mitigate that you could e.g. use HAproxy to front of two or more ES instances and point Kibana to the HAproxy hostname/port.
---
### Author:  [@Astro-es](https://discuss.elastic.co/u/Astro-es)
#### Post date: [November 17, 2015, 4:23am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/10 "2015-11-17T04:23:03Z")
Thanks,
Can it be added to feature request to pass the list of hosts to elasticsearch\_url so that it can automatically detect the master in case of failover?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 17, 2015, 4:24am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/11 "2015-11-17T04:24:43Z")
Sure, please raise a new issues here - [https://github.com/elastic/kibana/issues](https://github.com/elastic/kibana/issues) 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:08pm UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/12 "2017-07-06T14:08:55Z")