mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-29 01:44:36 -04:00
79e8aaec3d
This commit introduces a dedicated envirnoment variable ES_JAVA_HOME to determine the JDK used to start (if not using the bundled JDK). This environment variable will replace JAVA_HOME. The reason that we are making this change is because JAVA_HOME is a common environment variable and sometimes users have it set in their environment from other JDK applications that they have installed on their system. In this case, they would accidentally end up not using the bundled JDK despite their intentions. By using a dedicated environment variable specific to Elasticsearch, we avoid this potential for conflict. With this commit, we introduce the new environment variable, and deprecate the use of JAVA_HOME. We will remove support for JAVA_HOME in a future commit.
40 lines
1.3 KiB
Text
40 lines
1.3 KiB
Text
[horizontal]
|
|
`ES_JAVA_HOME`::
|
|
|
|
Set a custom Java path to be used.
|
|
|
|
`MAX_OPEN_FILES`::
|
|
|
|
Maximum number of open files, defaults to `65535`.
|
|
|
|
`MAX_LOCKED_MEMORY`::
|
|
|
|
Maximum locked memory size. Set to `unlimited` if you use the
|
|
`bootstrap.memory_lock` option in elasticsearch.yml.
|
|
|
|
`MAX_MAP_COUNT`::
|
|
|
|
Maximum number of memory map areas a process may have. If you use `mmapfs`
|
|
as index store type, make sure this is set to a high value. For more
|
|
information, check the
|
|
https://github.com/torvalds/linux/blob/master/Documentation/sysctl/vm.txt[linux kernel documentation]
|
|
about `max_map_count`. This is set via `sysctl` before starting
|
|
Elasticsearch. Defaults to `262144`.
|
|
|
|
`ES_PATH_CONF`::
|
|
|
|
Configuration file directory (which needs to include `elasticsearch.yml`,
|
|
`jvm.options`, and `log4j2.properties` files); defaults to
|
|
`/etc/elasticsearch`.
|
|
|
|
`ES_JAVA_OPTS`::
|
|
|
|
Any additional JVM system properties you may want to apply.
|
|
|
|
`RESTART_ON_UPGRADE`::
|
|
|
|
Configure restart on package upgrade, defaults to `false`. This means you
|
|
will have to restart your Elasticsearch instance after installing a
|
|
package manually. The reason for this is to ensure, that upgrades in a
|
|
cluster do not result in a continuous shard reallocation resulting in high
|
|
network traffic and reducing the response times of your cluster.
|