honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-25 17:38:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

[Docs] Add reason to use Settings API over config file (#32405)

Browse Source 
Extending the warning to prefer the `setttings` API over changes in the
configuration file by giving reasons why this might be dangerous.
This commit is contained in:
Christoph Büscher 2018-09-26 11:59:36 +02:00 committed by GitHub
parent eae5487477
commit 7bf216f4a1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/cluster/update-settings.asciidoc
View File

@ -108,9 +108,11 @@ The order of precedence for cluster settings is:
2. persistent cluster settings
3. settings in the `elasticsearch.yml` configuration file.
It's best to use the `elasticsearch.yml` file only
for local configurations, and set all cluster-wide settings with the
`settings` API.
It's best to set all cluster-wide settings with the `settings` API and use the
`elasticsearch.yml` file only for local configurations. This way you can be sure that
the setting is the same on all nodes. If, on the other hand, you define different
settings on different nodes by accident using the configuration file, it is very
difficult to notice these discrepancies.
You can find the list of settings that you can dynamically update in <<modules,Modules>>.