elasticsearch/docs/reference/setup/install/skip-set-kernel-parameters....

NOTE: On systemd-based distributions, the installation scripts will attempt to set kernel parameters (e.g.,
`vm.max_map_count`); you can skip this by masking the systemd-sysctl.service unit.
Add option to skip kernel parameters on install During package install on systemd-based systems, we try to set vm.max_map_count. On some systems (e.g., containers), users do not have the ability to tune these parameters from within the container. This commit provides an option for these users to skip setting such kernel parameters. Relates #21899 2016-12-02 06:23:51 +08:00			`NOTE: On systemd-based distributions, the installation scripts will attempt to set kernel parameters (e.g.,`
Honor masking of systemd-sysctl.service During package install on systemd-based systems, some sysctl settings should be set (e.g. vm.max_map_count). In some environments, changing sysctl settings plainly does not work; previously a global environment variable named ES_SKIP_SET_KERNEL_PARAMETERS was introduced to skip calling sysctl, but this causes trouble for: - configuration management systems, which usually cannot apply an env var when running a package manager - package upgrades, which will not have the env var set any more, and thus leaving the package management system in a bad state (possibly half-way upgraded, can be very hard to recover) This removes the env var again and instead of calling systemd-sysctl manually, tells systemd to restart the wrapper unit - which itself can be masked by system administrators or management tools if it is known that sysctl does not work in a given environment. The restart is not silent on systems in their default configuration, but is ignored if the unit is masked. Relates #24234 2017-06-06 22:44:41 +08:00			`vm.max_map_count`); you can skip this by masking the systemd-sysctl.service unit.