Cluster settings

Introduced 1.0

The cluster settings operation lets you check the current settings for your cluster, review default settings, and change settings. When you update a setting using the API, OpenSearch applies it to all nodes in the cluster.

Path and HTTP methods

  1. GET _cluster/settings
  2. PUT _cluster/settings

Path parameters

All cluster setting parameters are optional.

ParameterData typeDescription
flat_settingsBooleanWhether to return settings in the flat form, which can improve readability, especially for heavily nested settings. For example, the flat form of “cluster”: { “max_shards_per_node”: 500 } is “cluster.max_shards_per_node”: “500”.
include_defaults (GET only)BooleanWhether to include default settings as part of the response. This parameter is useful for identifying the names and current values of settings you want to update.
cluster_manager_timeoutTime unitThe amount of time to wait for a response from the cluster manager node. Default is 30 seconds.
timeout (PUT only)Time unitThe amount of time to wait for a response from the cluster. Default is 30 seconds.

Example request

  1. GET _cluster/settings?include_defaults=true

copy

Example response

  1. PUT _cluster/settings
  2. {
  3. "persistent":{
  4. "action.auto_create_index": false
  5. }
  6. }

Request fields

The GET operation has no request body options. All cluster setting field parameters are optional.

Not all cluster settings can be updated using the cluster settings API. You will receive the error message "setting [cluster.some.setting], not dynamically updateable" when trying to configure these settings through the API.

For a listing of all cluster settings, see Configuring OpenSearch.

Example request

For a PUT operation, the request body must contain transient or persistent, along with the setting you want to update:

  1. PUT _cluster/settings
  2. {
  3. "persistent":{
  4. "cluster.max_shards_per_node": 500
  5. }
  6. }

copy

For more information about transient settings, persistent settings, and precedence, see OpenSearch configuration.

Example response

  1. {
  2. "acknowledged":true,
  3. "persistent":{
  4. "cluster":{
  5. "max_shards_per_node":"500"
  6. }
  7. },
  8. "transient":{}
  9. }