-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Remove option to configure custom config file via CONF_FILE or -Des.default.conf #13772
Conversation
loadFromEnv = false; | ||
output.loadFromPath(environment.configFile().resolve(System.getProperty("elasticsearch.config"))); | ||
} | ||
} | ||
if (loadFromEnv) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the local loadFromEnv
and be removed?
LGTM, I left a couple very minor comments. |
@test "[$GROUP] start elasticsearch with a custom CONFIG_FILE and check failure" { | ||
local CONF_FILE="$ESCONFIG/elasticsearch.yml" | ||
|
||
if is_dpkg ; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No space here I think.
I also left some pretty minor comments. |
Where does the systemd pre-exec file come from ? edit: ignore me; found it now. seems i missed it when browsing on my mobile. |
3c59858
to
457877b
Compare
@nik9000 @rjernst thanks for the review! addressed all comments. |
Chatted with @spinscale who wanted the check for |
6998e65
to
988f445
Compare
@rjernst or @nik9000 or @spinscale can you take another look? |
Forgot to add that I tried out the service.bat on windows now too. Thanks @dliappis for the help! |
988f445
to
8d4bd94
Compare
LGTM |
…efault.conf It is rarely used and was not consistently handled by different distributions anyway. This commit also adds a test for specifying CONF_DIR when installing plugins and starting elasticsearch. relates to elastic#12712 and elastic#12954 closes elastic#5329 closes elastic#13715
# $1 expected status code | ||
# $2 additional command line args | ||
run_elasticsearch_service() { | ||
# Set the CONF_DIR setting in case we start as a service |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd probably save $1 and $2 to named variables because they can get confusing lower down.
elif is_sysvinit; then | ||
run service elasticsearch status | ||
[ "$status" -eq 0 ] | ||
[ "$status" -eq $1 ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would be clearer is $1
were $expected_status
or something.
@nik9000 addressed all comments. I made the timeout now dependent on if we run in background or not but my bash is that of a 3 year old so if you have any suggestion to improve readability don't hold back. |
LGTM |
Remove option to configure custom config file via CONF_FILE or -Des.default.conf
…efault.conf It is rarely used and was not consistently handled by different distributions anyway. This commit also adds a test for specifying CONF_DIR when installing plugins and starting elasticsearch. relates to #12712 and #12954 closes #5329 closes #13715 Merge pull request #13772 from brwe/remove-CONF_FILE
…efault.conf It is rarely used and was not consistently handled by different distributions anyway. This commit also adds a test for specifying CONF_DIR when installing plugins and starting elasticsearch. relates to #12712 and #12954 closes #5329 closes #13715 Merge pull request #13772 from brwe/remove-CONF_FILE
…efault.conf It is rarely used and was not consistently handled by different distributions anyway. This commit also adds a test for specifying CONF_DIR when installing plugins and starting elasticsearch. relates to #12712 and #12954 closes #5329 closes #13715 Merge pull request #13772 from brwe/remove-CONF_FILE
This was actually a feature we used and this required me to re-architecture our cluster deployment. I have no idea why, in 2015, you would remove the ability to specify a config file, and instead for the user to have a config file be a specific filename. Obviously the damage is done, but I would dispute the claim that it is 'It is rarely used' |
It is rarely used and was not consistently handled by different distributions anyway.
This commit also adds a test for specifying CONF_DIR when installing plugins and
starting elasticsearch.
relates to #12712 and #12954
closes #5329
closes #13715
Would be great if someone with a windows machine could test the bat file, I unfortunately can't.