Reflect changes in systemd service for LimitMEMLOCK

The LimitMEMLOCK suggestion was removed from systemd service file and
instead users should use an override file, so a comment in the
environment file should be updated to reflect the same.

Relates #27630
This commit is contained in:
ajrpayne 2017-12-03 06:20:10 -08:00 committed by Jason Tedor
parent cd67f6a8d7
commit a880bbd57d
1 changed files with 2 additions and 2 deletions

View File

@ -41,8 +41,8 @@ ES_STARTUP_SLEEP_TIME=5
# The maximum number of bytes of memory that may be locked into RAM
# Set to "unlimited" if you use the 'bootstrap.memory_lock: true' option
# in elasticsearch.yml.
# When using Systemd, the LimitMEMLOCK property must be set
# in /usr/lib/systemd/system/elasticsearch.service
# When using systemd, LimitMEMLOCK must be set in a unit file such as
# /etc/systemd/system/elasticsearch.service.d/override.conf.
#MAX_LOCKED_MEMORY=unlimited
# Maximum number of VMA (Virtual Memory Areas) a process can own