From 93d63b9b7de07e041b3d5d0b9986aa1eec44bbfb Mon Sep 17 00:00:00 2001 From: Giovanni Geraci Date: Wed, 16 Jun 2021 03:43:34 +0200 Subject: [PATCH] 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> --- docs/user/production-considerations/production.asciidoc | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/user/production-considerations/production.asciidoc b/docs/user/production-considerations/production.asciidoc index 1ffca4b6ae6a..b75b556588cf 100644 --- a/docs/user/production-considerations/production.asciidoc +++ b/docs/user/production-considerations/production.asciidoc @@ -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] --------