2016-04-03 22:09:24 +08:00
|
|
|
[horizontal]
|
2021-02-18 01:41:23 +08:00
|
|
|
`ES_JAVA_HOME`::
|
2016-04-07 05:06:30 +08:00
|
|
|
|
|
|
|
Set a custom Java path to be used.
|
|
|
|
|
2017-08-15 05:19:06 +08:00
|
|
|
`ES_PATH_CONF`::
|
2016-04-03 22:09:24 +08:00
|
|
|
|
2017-08-15 05:19:06 +08:00
|
|
|
Configuration file directory (which needs to include `elasticsearch.yml`,
|
|
|
|
`jvm.options`, and `log4j2.properties` files); defaults to
|
|
|
|
`/etc/elasticsearch`.
|
2016-04-03 22:09:24 +08:00
|
|
|
|
|
|
|
`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
|
2017-11-29 16:44:25 +08:00
|
|
|
will have to restart your Elasticsearch instance after installing a
|
2016-04-03 22:09:24 +08:00
|
|
|
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.
|