# Roundrobin kibana names **URL:** \ **Category:** Kibana\ **Created:** [June 27, 2019, 1:51pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857 "2019-06-27T13:51:21Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [June 27, 2019, 1:51pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/1 "2019-06-27T13:51:21Z")
I have three kibana server kib01, kib02, kib03 ( 10.x.x.1, 10.x.x.2, 10.x.x.3) I did setup dns for them kibglobal -\> 10.x.x.1 kibglobal -\> 10.x.x.2 kibglobal -\> 10.x.x.3 now when I do nslooking I get all this ip in different order. problem here is that when I run [http://kibglobal:5601](http://kibglobal:5601) -\> it is very very slow but if I do [http://kib01:5601](http://kib01:5601) it works as expacted. Am I write on track for this kind of setup? I have following in each hosts kibana.yml file as well elasticsearch.hosts: ["[http://elkm01:9200](http://elkm01:9200)","[http://elkm02:9200](http://elkm02:9200)","[http://elkm03:9200](http://elkm03:9200)"] ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [June 27, 2019, 7:07pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/2 "2019-06-27T19:07:09Z")
It logs me out every few second. is there a some setting that bind me to that session for longer time I am using 7.1.1 ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [June 27, 2019, 7:35pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/3 "2019-06-27T19:35:04Z")
These are the messages in kibana.log essage":"GET /logout?next=%2Fapp%2Fkibana%23%2Fdashboards%3F\_g%3D()&msg=SESSION\_EXPIRED 200 21ms - 9.0B"} msg=SESSION\_EXPIRED"},"res":{"statusCode":304,"responseTime":1,"contentLength":9},"message":"GET /node\_modules/@elastic/eui/dist/eui\_theme\_light.css 304 1ms - 9.0B"} ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [June 28, 2019, 3:46pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/4 "2019-06-28T15:46:30Z")
Other observation. I have three different cluster, each has three node. This kind of problem is only on one cluster. can't figure out what is wrong. I guess no one else is using such a thing ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [June 28, 2019, 5:48pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/5 "2019-06-28T17:48:03Z")
> [@elasticforme](#): > > I get all this ip in different order. > > problem here is that when I run > [http://kibglobal:5601](http://kibglobal:5601) -\> it is very very slow > but if I do [http://kib01:5601](http://kib01:5601) it works as expacted. @jbudz - any idea here ? ---
**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:** [June 28, 2019, 9:37pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/6 "2019-06-28T21:37:48Z")
Were you able to verify all of the kibana instances are not slow when connecting directly (not sure if the comment was referring to clusters or kibana's)? What are you using for your DNS setup? Regarding the logouts, you'll want xpack.security.encryptionKey to be the same across alll kibana instances. If it's not set, it'll be generated. Kibana stores session information in an encrypted cookie, and you'll get timeouts if your server switches ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [July 1, 2019, 2:59pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/7 "2019-07-01T14:59:18Z")
yes all individual link to host works fine and it does not get time out or logout. Sorry didn't explain in more detail I have elk01, elk02, elk03 (master/data node for elasticsearch, all three running kibana as well) version 7.1.1 now on dns they are elk01 \<--\> ip1 (forward and reverse set elk02 \<--\> ip2 elk03 \<--\> ip3 now set up one name which point to all three ip. elk -\> ip1 elk -\> ip2 elk -\> ip3 Goal here is that user can type elk:5601 and should able to hit any server. No I don't have any xpack.security.encryptionKey setup. in kibana.yml I have identical setup on other four center and it works on three center without any problem. I have check and recheck my setup, compare config with other setup and they all looks same. ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [July 8, 2019, 5:42pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/8 "2019-07-08T17:42:34Z")
@jbudz any insight about it? just giving bump to thread ---
**Author:** ![martinr\_ubi](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@martinr\_ubi](https://discuss.elastic.co/u/martinr_ubi)\ **Post date:** [July 8, 2019, 6:01pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/9 "2019-07-08T18:01:53Z")
> [@elasticforme](#): > > No I don't have any xpack.security.encryptionKey setup. in kibana.yml You need to set this. I too have 3 kibanas behind a load balancer, in your case its DNS round robin but the end result is the same, requests can move around the kibana hosts if you have more than 1. This setting is required when you have more than 1 kibana or else they can’t all decrypt each others cookies. Which breaks the frontend when you randomly go to another kibana instance. ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [July 9, 2019, 2:53pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/10 "2019-07-09T14:53:08Z")
> [@martinr\_ubi](#): > > I too have 3 kibanas behind a load balancer What is that load balancer? is it some kind of app? ---
**Author:** ![martinr\_ubi](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@martinr\_ubi](https://discuss.elastic.co/u/martinr_ubi)\ **Post date:** [July 9, 2019, 3:49pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/11 "2019-07-09T15:49:16Z")
AWS ELB My ES cluster runs on AWS ECS (docker containers) and my Kibana too. So I have 3 Kibana docker containers running that are considered a "Service" with desired count = 3 in AWS ECS and they are fronted by an AWS ELB which load balances to all 3 kibana containers. ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [July 9, 2019, 7:55pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/12 "2019-07-09T19:55:59Z")
Great it works with that key. even when I shutdown kibana on one server it fails over to second and without delay I get response and result back. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 6, 2019, 7:57pm UTC](https://discuss.elastic.co/t/roundrobin-kibana-names/187857/13 "2019-08-06T19:57:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.