Unlike Kibana 3, Kibana 4 stores user session state in the Kibana server. Is that accurate?
If this is true, how would one load balance Kibana? I could configure my load balancer to be sticky, but that would require me to terminate SSL at the LB, not Kibana, something I can't do.
I think I can get around this by setting the following fields:
elasticsearch.preserveHost: true server.host: ipOfKibanaHostNotLoadBalancer
If Kibana is storing session state in its server, I believe this will ensure that all requests go back to the server that served up this config file. So, as long as the user doesn't do a hard browser refresh, they should always hit the same server.
Can you tell me if this is accurate? What is stored in session state? What are the consequences of doing a hard-refresh in the browser and getting sent to a different Kibana server?