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

Custom config path for elasticsearch 6.0 not working #20717

Closed
khakulov opened this issue Nov 16, 2017 · 3 comments · Fixed by #20735
Closed

Custom config path for elasticsearch 6.0 not working #20717

khakulov opened this issue Nov 16, 2017 · 3 comments · Fixed by #20735

Comments

@khakulov
Copy link

khakulov commented Nov 16, 2017

The command ES_PATH_CONF=$PWD/elasticsearch_config elasticsearch not working anymore.

My workaround for now is

ES_PATH_CONF=$PWD/elasticsearch_config /usr/local/Cellar/elasticsearch/6.0.0/libexec/bin/elasticsearch

But the path /usr/local/Cellar/elasticsearch/6.0.0/ is very specific for my Mac OSX and eventually does not work on other systems.

I also copied jvm.options file to my config folder to fix java errors. This step was not necessary for ES 5.

related pull request elastic/elasticsearch#21932

@ilovezfs
Copy link
Contributor

@jasontedor any ideas here what we should do?

@jasontedor
Copy link
Contributor

jasontedor commented Nov 17, 2017

Thanks for the report @khakulov. Thanks for the ping @ilovezfs. This is from elastic/elasticsearch#25815 (and the follow on elastic/elasticsearch#26197 that only renamed CONF_DIR to ES_PATH_CONF). I will open a PR here soon to address.

@jasontedor
Copy link
Contributor

I opened #20735.

ilovezfs pushed a commit that referenced this issue Nov 17, 2017
This commit fixes an issue with setting a custom config path via
ES_PATH_CONF.

Fixes #20717.
@Homebrew Homebrew locked and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants