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] Edits load balancing section of production docs (#143481)

Browse source
This commit is contained in:
gchaps 2022-10-18 10:58:22 -07:00 • committed by GitHub
parent 253ed9c398
commit 8741acef54
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/user/production-considerations/production.asciidoc
View file

@ -27,16 +27,11 @@ you can configure {kib} to use a list of {es} hosts.
To serve multiple {kib} installations behind a load balancer, you must change the configuration.
See {kibana-ref}/settings.html[Configuring {kib}] for details on each setting.
Settings unique across each {kib} instance:
These settings must be unique across each {kib} instance:
[source,js]
--------
server.uuid
server.uuid // if not provided, this is autogenerated
server.name
--------
Settings unique across each host (for example, running multiple installations on the same virtual machine):
[source,js]
--------
path.data
pid.file
server.port
@ -106,7 +101,7 @@ These can be used to automatically update the list of hosts as a cluster is resi
[[memory]]
=== Memory
Kibana has a default memory limit that scales based on total memory available. In some scenarios, such as large reporting jobs,
Kibana has a default memory limit that scales based on total memory available. In some scenarios, such as large reporting jobs,
it may make sense to tweak limits to meet more specific requirements.
A limit can be defined by setting `--max-old-space-size` in the `node.options` config file found inside the `kibana/config` folder or any other folder configured with the environment variable `KBN_PATH_CONF`. For example, in the Debian-based system, the folder is `/etc/kibana`.