-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Some cluster settings don't take effect if set from elasticsearch.yml, but work fine if set via API #40803
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
Comments
Pinging @elastic/es-core-infra |
Can confirm bug. Part of exception: Current solution: |
And when I`m trying:
Got error: |
@Pupkur That looks like an issue with OpenDistro, which we don't maintain and can't provide support for. We do our best to answer questions about our default distribution and core Elasticsearch functionality on our forums and address bugs here on GitHub, but for third-party plugins you'll need to get support from either the creator of the plugin or a community with knowledge about that plugin. Let's keep the discussion on this issue focused on the bug described in the first post. |
This comment has been minimized.
This comment has been minimized.
We are having the same issue, we can work around this using the API but thats an issue. We are on 7.7. Is there a specific section of the yml that this should be in? When placing this setting in the yml we were not sure where to place it. I don't think that should matter but wanted to check. |
The |
If someone work in Kibana curl: |
@gwbrown I don't think this is the right reasoning to use here. I think we shouldn't silently ignore settings like this, regardless of how likely they are to be used. In this case, you might for instance expect to be able to use this setting to bring up a cluster in a purely read-only mode -- perhaps you want to do some forensic analysis on a snapshot of the cluster and be sure that the data will remain unchanged while you're doing it. I think that silently ignoring this setting would be surprising to users trying to do that. I'm reopening this issue for that reason. |
Hi! I run the ELK stack under the 7.8.1 version, and I get the same problem. Thanks ! |
Any plans to fix this, ticket has been open for ever 2 years. |
We can fix the |
Pinging @elastic/es-core-infra (Team:Core/Infra) |
During a team meeting, we discussed that some sort of validation, or some sort of general solution is needed here. However, the solution here isn't obvious as this would likely require breaking changes, and will need more thought/design. The biggest challenge here be finding consensus from the broader team on how this should work. |
Uh oh!
There was an error while loading. Please reload this page.
Some cluster-level settings don't take effect unless they're set via the Cluster Settings API, and values specified in
elasticsearch.yml
are ignored. They'll show up inGET _cluster/settings?include_defaults=true
but will be otherwise ignored.This is caused by reading settings only from the cluster state - in order to be initialized in
elasticsearch.yml
, a variable needs to be set in memory and initialized from a differentSettings
object during startup and updated in a cluster state listener rather than being read directly from the cluster state.So far, I've found these settings which don't respect values set in
elasticsearch.yml
:cluster.blocks.read_only
fixed in #57234.cluster.max_shards_per_node
/cc @joegallo who pointed this out
The text was updated successfully, but these errors were encountered: