github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 01:38:56 -04:00
Code Issues Projects Releases Packages Wiki Activity

[docs/production] multiple es nodes (#30276)

Browse source 
* [docs/production] multiple es nodes

* note console limitation

* mention related configuration
This commit is contained in:
Jonathan Budzenski 2019-06-24 12:58:46 -05:00 • committed by Jonathan Budzenski
parent 4a9fd0f8ba
commit e8ca0cad1f
No known key found for this signature in database
GPG key ID: D28BF9418FA0F292
1 changed files with 19 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/setup/production.asciidoc
View file

@ -5,6 +5,7 @@
* <<csp-strict-mode>>
* <<enabling-ssl>>
* <<load-balancing>>
* <<high-availability>>
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
@ -109,3 +110,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].