a3da48de12
* Remove recommendation of coordinating only node A documentation should be easy and straight forward and giving the user the easiest possible way to get to a fully functioning cluster. Running a coordinating only node is a bad idea because: 1. Introduces a single point of failure, especially when it is running on the same host as Kibana. 2. Introduces complexity, because you need to run an additional node. The easiest way to solve the issue of load balancing is to add multiple hosts in the `Elasticsearch.hosts` array in the `Kibana.yml`. This should be far easier than deploying a coordinating node. * fixed CI errors, there were references to the deleted `load-balancing-es` https://github.com/elastic/kibana/pull/100632 Co-authored-by: Philipp Kahr <philipp.kahr@elastic.co> |
||
|---|---|---|
| .. | ||
| api | ||
| apm | ||
| canvas | ||
| code | ||
| concepts | ||
| dev-tools | ||
| developer | ||
| development | ||
| discover | ||
| fleet | ||
| getting-started | ||
| images | ||
| management | ||
| maps | ||
| migration | ||
| observability | ||
| settings | ||
| setup | ||
| siem | ||
| spaces | ||
| uptime/images | ||
| user | ||
| visualize/images | ||
| accessibility.asciidoc | ||
| action-type-template.asciidoc | ||
| CHANGELOG.asciidoc | ||
| glossary.asciidoc | ||
| gs-index.asciidoc | ||
| index.asciidoc | ||
| index.x.asciidoc | ||
| limitations.asciidoc | ||
| migration.asciidoc | ||
| redirects.asciidoc | ||
| release-notes.asciidoc | ||
| rule-type-template.asciidoc | ||
| timelion.asciidoc | ||