From 4a583cec4fad446515ed09a4cc91f4ba23b13367 Mon Sep 17 00:00:00 2001 From: Jonathan Budzenski Date: Mon, 24 Jun 2019 12:58:46 -0500 Subject: [PATCH] [docs/production] multiple es nodes (#30276) * [docs/production] multiple es nodes * note console limitation * mention related configuration --- docs/setup/production.asciidoc | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/setup/production.asciidoc b/docs/setup/production.asciidoc index 9158b1ae2197..d3d24e8c41da 100644 --- a/docs/setup/production.asciidoc +++ b/docs/setup/production.asciidoc @@ -5,6 +5,7 @@ * <> * <> * <> +* <> How you deploy Kibana largely depends on your use case. If you are the only user, you can run Kibana on your local machine and configure it to point to whatever @@ -107,3 +108,21 @@ transport.tcp.port: 9300 - 9400 # The Elasticsearch instance to use for all your queries. elasticsearch.hosts: ["http://localhost:9200"] -------- + +[float] +[[high-availability]] +=== High Availability Across Multiple Elasticsearch Nodes +Kibana can be configured to connect to multiple Elasticsearch nodes in the same cluster. In situations where a node becomes unavailable, +Kibana will transparently connect to an available node and continue operating. Requests to available hosts will be routed in a round robin fashion. + +Currently the Console application is limited to connecting to the first node listed. + +In kibana.yml: +-------- +elasticsearch.hosts: + - http://elasticsearch1:9200 + - http://elasticsearch2:9200 +-------- + +Related configurations include `elasticsearch.sniffInterval`, `elasticsearch.sniffOnStart`, and `elasticsearch.sniffOnConnectionFault`. +These can be used to automatically update the list of hosts as a cluster is resized. Parameters can be found on the {kibana-ref}/settings.html[settings page]. \ No newline at end of file