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

envdir doesn't appear to work as is for all sv-run scripts #19

Open
dearing opened this issue Aug 1, 2015 · 3 comments
Open

envdir doesn't appear to work as is for all sv-run scripts #19

dearing opened this issue Aug 1, 2015 · 3 comments
Assignees
Labels

Comments

@dearing
Copy link
Owner

dearing commented Aug 1, 2015

Seems like configured values trump environment vars; more testing needed.

@dearing dearing added the bug label Aug 1, 2015
@dearing dearing self-assigned this Aug 1, 2015
@dearing dearing modified the milestone: v0.3.3 Aug 2, 2015
@dearing dearing added question and removed bug labels Aug 7, 2015
@akadoya
Copy link

akadoya commented Apr 14, 2016

it seems like $ES_HOME/bin/elasticsearch.in.sh is overriding those values

@dearing
Copy link
Owner Author

dearing commented Apr 20, 2016

I'm on a bit of a vacation still and will check into things when I get back.

@akadoya
Copy link

akadoya commented Apr 23, 2016

I could apply all of the settings by passing environment variables to elasticsearch.in.sh.
I think this is the only case for Ubuntu, but for tweaking MAX_OPEN_FILES and MAX_LOCKED_MEMORY, I also had to change the configuration of ulimit, pam_limits(/etc/pam.d/common-session*) and sv-elasticsearch-run.erb to let runit spawn sudo session so that limits.conf configuration will be applied to elasticsearch process.
I couldn't make chpst work along with ulimit tweaks but there could be smarter way.

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

No branches or pull requests

2 participants