Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LimitMEMLOCK and LimitNOFILE aren't being set on elasticsearch.service #1117

Open
mmack000 opened this issue Mar 25, 2021 · 1 comment
Open

Comments

@mmack000
Copy link

Does the 7.0.0 module manage the default elasticsearch.service? We were using instances prior to 7.0.0 of the module. The reason I ask, when setting init_defaults, elasticsearch fails as the same mem lock settings aren't being set on the elasticsearch.service. This was something that worked prior to 7.0.0.

init_defaults
MAX_LOCKED_MEMORY: 'unlimited'
MAX_OPEN_FILES: '1048576'

  • Module version: 7.0.0
@adamwalz
Copy link

@mmack000 I ran into this same problem. No, the 7.0.0 module no longer manages the elasticsearch.service systemd unit file. A drop-in can be used instead to override the defaults https://github.com/voxpupuli/puppet-systemd#drop-in-files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants