Some cluster settings don't take effect if set from elasticsearch.yml, but work fine if set via API
#40 803 ouverte le 3 avr. 2019
Métriques du dépôt
- Stars
- (76 700 stars)
- Métriques de merge PR
- (Merge moyen 2j) (1 000 PRs mergées en 30 j)
Description
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 in GET _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 different Settings 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
cluster.max_shards_per_node
/cc @joegallo who pointed this out