sysconfig-file.asciidoc 1.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455
  1. [horizontal]
  2. `ES_USER`::
  3. The user to run as, defaults to `elasticsearch`.
  4. `ES_GROUP`::
  5. The group to run as, defaults to `elasticsearch`.
  6. `JAVA_HOME`::
  7. Set a custom Java path to be used.
  8. `MAX_OPEN_FILES`::
  9. Maximum number of open files, defaults to `65536`.
  10. `MAX_LOCKED_MEMORY`::
  11. Maximum locked memory size. Set to `unlimited if you use the
  12. `bootstrap.mlockall` option in elasticsearch.yml.
  13. `MAX_MAP_COUNT`::
  14. Maximum number of memory map areas a process may have. If you use `mmapfs`
  15. as index store type, make sure this is set to a high value. For more
  16. information, check the
  17. https://github.com/torvalds/linux/blob/master/Documentation/sysctl/vm.txt[linux kernel documentation]
  18. about `max_map_count`. This is set via `sysctl` before starting
  19. elasticsearch. Defaults to `262144`.
  20. `LOG_DIR`::
  21. Log directory, defaults to `/var/log/elasticsearch`.
  22. `DATA_DIR`::
  23. Data directory, defaults to `/var/lib/elasticsearch`.
  24. `CONF_DIR`::
  25. Configuration file directory (which needs to include `elasticsearch.yml`
  26. and `logging.yml` files), defaults to `/etc/elasticsearch`.
  27. `ES_JAVA_OPTS`::
  28. Any additional JVM system properties you may want to apply.
  29. `RESTART_ON_UPGRADE`::
  30. Configure restart on package upgrade, defaults to `false`. This means you
  31. will have to restart your elasticsearch instance after installing a
  32. package manually. The reason for this is to ensure, that upgrades in a
  33. cluster do not result in a continuous shard reallocation resulting in high
  34. network traffic and reducing the response times of your cluster.