OpenSearch/docs/reference/cluster/update-settings.asciidoc

113 lines
2.9 KiB
Plaintext
Raw Normal View History

[[cluster-update-settings]]
== Cluster Update Settings
Allows to update cluster wide specific settings. Settings updated can
either be persistent (applied cross restarts) or transient (will not
survive a full cluster restart). Here is an example:
[source,js]
--------------------------------------------------
PUT /_cluster/settings
{
"persistent" : {
"indices.recovery.max_bytes_per_sec" : "50mb"
}
}
--------------------------------------------------
// CONSOLE
Or:
[source,js]
--------------------------------------------------
PUT /_cluster/settings?flat_settings=true
{
"transient" : {
"indices.recovery.max_bytes_per_sec" : "20mb"
}
}
--------------------------------------------------
// CONSOLE
The cluster responds with the settings updated. So the response for the
last example will be:
[source,js]
--------------------------------------------------
{
...
"persistent" : { },
"transient" : {
"indices.recovery.max_bytes_per_sec" : "20mb"
}
}
--------------------------------------------------
// TESTRESPONSE[s/\.\.\./"acknowledged": true,/]
2015-12-07 15:19:40 -05:00
Resetting persistent or transient settings can be done by assigning a
`null` value. If a transient setting is reset, the persistent setting
is applied if available. Otherwise Elasticsearch will fallback to the setting
defined at the configuration file or, if not existent, to the default
value. Here is an example:
[source,js]
--------------------------------------------------
PUT /_cluster/settings
{
2015-12-07 15:19:40 -05:00
"transient" : {
"indices.recovery.max_bytes_per_sec" : null
2015-12-07 15:19:40 -05:00
}
}
2015-12-07 15:19:40 -05:00
--------------------------------------------------
// CONSOLE
2015-12-07 15:19:40 -05:00
Reset settings will not be included in the cluster response. So
the response for the last example will be:
[source,js]
--------------------------------------------------
{
...
2015-12-07 15:19:40 -05:00
"persistent" : {},
"transient" : {}
}
2015-12-09 06:24:40 -05:00
--------------------------------------------------
// TESTRESPONSE[s/\.\.\./"acknowledged": true,/]
2015-12-09 06:24:40 -05:00
Settings can also be reset using simple wildcards. For instance to reset
all dynamic `indices.recovery` setting a prefix can be used:
2015-12-09 06:24:40 -05:00
[source,js]
--------------------------------------------------
PUT /_cluster/settings
{
2015-12-09 06:24:40 -05:00
"transient" : {
"indices.recovery.*" : null
2015-12-09 06:24:40 -05:00
}
}
2015-12-09 06:24:40 -05:00
--------------------------------------------------
// CONSOLE
2015-12-07 15:19:40 -05:00
Cluster wide settings can be returned using:
[source,js]
--------------------------------------------------
GET /_cluster/settings
--------------------------------------------------
// CONSOLE
[float]
=== Precedence of settings
Transient cluster settings take precedence over persistent cluster settings,
which take precedence over settings configured in the `elasticsearch.yml`
config file.
For this reason it is preferrable to use the `elasticsearch.yml` file only
for local configurations, and set all cluster-wider settings with the
`settings` API.
A list of dynamically updatable settings can be found in the
<<modules,Modules>> documentation.