You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Anand Subramanian (JIRA)" <ji...@apache.org> on 2018/01/12 13:56:00 UTC
[jira] [Created] (METRON-1399) ES 5.x requires additional
configuration for OS' which use systemd
Anand Subramanian created METRON-1399:
-----------------------------------------
Summary: ES 5.x requires additional configuration for OS' which use systemd
Key: METRON-1399
URL: https://issues.apache.org/jira/browse/METRON-1399
Project: Metron
Issue Type: Bug
Affects Versions: 0.4.3
Reporter: Anand Subramanian
This is with latest master, which has elasticsearch 5.6.2.
On a Centos 7, it is seen that the Elasticsearch service fails to start with error as follows:
{code}
[2017-12-07T10:06:36,451][ERROR][o.e.b.Bootstrap ] [metron-1.openstacklocal] node validation exception
[1] bootstrap checks failed
[1]: memory locking requested for elasticsearch process but memory is not locked
[2017-12-07T10:06:36,459][INFO ][o.e.n.Node ] [metron-1.openstacklocal] stopping ...
[2017-12-07T10:06:36,496][INFO ][o.e.n.Node ] [metron-1.openstacklocal] stopped
[2017-12-07T10:06:36,497][INFO ][o.e.n.Node ] [metron-1.openstacklocal] closing ...
[2017-12-07T10:06:36,522][INFO ][o.e.n.Node ] [metron-1.openstacklocal] closed
{code}
There was no change in behavior after adding the entry "MAX_LOCKED_MEMORY=unlimited" in /etc/sysconfig/elasticsearch.
I found that ES 5.x requires additional configuration for environments that use systemd (like CentOS 7). The following link explains the changes required:
https://www.elastic.co/guide/en/elasticsearch/reference/master/setting-system-settings.html#systemd
This hence needs to be done at install/configuration time for ES to come up properly on OS' that use 'systemd'.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)