Remove old limit on Console application (#100882)
In latest stable version of Kibana(7.13), Console application seems to be not limited anymore to connecting only to the first host defined in elasticsearch.hosts defined on kibana.yml. On previous Kibana releases, if the first Elasticsearch host was not available(i.e. maintenance or failure), Console application was returning an error: "Client request error: connect EHOSTUNREACH". Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
This commit is contained in:
parent
4cf6bca01e
commit
93d63b9b7d
1 changed files with 0 additions and 2 deletions
|
@ -122,8 +122,6 @@ active in case of failure from the currently used instance.
|
|||
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:
|
||||
[source,js]
|
||||
--------
|
||||
|
|
Loading…
Reference in a new issue