| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209 | [[cluster-update-settings]]== Cluster Update SettingsAllows to update cluster wide specific settings. Settings updated caneither be persistent (applied cross restarts) or transient (will notsurvive a full cluster restart). Here is an example:[source,js]--------------------------------------------------curl -XPUT localhost:9200/_cluster/settings -d '{    "persistent" : {        "discovery.zen.minimum_master_nodes" : 2    } }' --------------------------------------------------Or:[source,js]--------------------------------------------------curl -XPUT localhost:9200/_cluster/settings -d '{    "transient" : {        "discovery.zen.minimum_master_nodes" : 2    } }' --------------------------------------------------The cluster responds with the settings updated. So the response for thelast example will be:[source,js]--------------------------------------------------{    "persistent" : {},    "transient" : {        "discovery.zen.minimum_master_nodes" : "2"    } }' --------------------------------------------------Cluster wide settings can be returned using:[source,js]--------------------------------------------------curl -XGET localhost:9200/_cluster/settings--------------------------------------------------There is a specific list of settings that can be updated, those include:[float][[cluster-settings]]=== Cluster settings[float]==== Routing allocation[float]===== Awareness`cluster.routing.allocation.awareness.attributes`::     See <<modules-cluster>>.`cluster.routing.allocation.awareness.force.*`::     See <<modules-cluster>>.[float]===== Balanced Shards`cluster.routing.allocation.balance.shard`::     Defines the weight factor for shards allocated on a node      (float). Defaults to `0.45f`.`cluster.routing.allocation.balance.index`::     Defines a factor to the number of shards per index allocated       on a specific node (float). Defaults to `0.5f`.`cluster.routing.allocation.balance.primary`::      defines a weight factor for the number of primaries of a specific index       allocated on a node (float). `0.05f`.`cluster.routing.allocation.balance.threshold`::      minimal optimization value of operations that should be performed (non       negative float). Defaults to `1.0f`.[float]===== Concurrent Rebalance`cluster.routing.allocation.cluster_concurrent_rebalance`::       Allow to control how many concurrent rebalancing of shards are        allowed cluster wide, and default it to `2` (integer). `-1` for        unlimited. See also <<modules-cluster>>.[float]===== Disable allocationadded[1.0.0.RC1]All the disable allocation settings have been deprecated in favour for`cluster.routing.allocation.enable` setting.`cluster.routing.allocation.disable_allocation`::     See <<modules-cluster>>.`cluster.routing.allocation.disable_replica_allocation`::     See <<modules-cluster>>.`cluster.routing.allocation.disable_new_allocation`::     See <<modules-cluster>>.[float]===== Enable allocation`cluster.routing.allocation.enable`::     See <<modules-cluster>>.[float]===== Throttling allocation`cluster.routing.allocation.node_initial_primaries_recoveries`::     See <<modules-cluster>>.`cluster.routing.allocation.node_concurrent_recoveries`::     See <<modules-cluster>>.[float]===== Filter allocation`cluster.routing.allocation.include.*`::     See <<modules-cluster>>.`cluster.routing.allocation.exclude.*`::     See <<modules-cluster>>.`cluster.routing.allocation.require.*`      See <<modules-cluster>>.[float]==== Metadata`cluster.blocks.read_only`::      Have the whole cluster read only (indices do not accept write operations), metadata is not allowed to be modified (create or delete indices).[float]==== Discovery`discovery.zen.minimum_master_nodes`::     See <<modules-discovery-zen>>[float]==== Threadpools`threadpool.*`::     See <<modules-threadpool>>[float][[cluster-index-settings]]=== Index settings[float]==== Index filter cache`indices.cache.filter.size`::     See <<index-modules-cache>>`indices.cache.filter.expire` (time)::     See <<index-modules-cache>>[float]==== TTL interval`indices.ttl.interval` (time)::     See <<mapping-ttl-field>>[float]==== Recovery`indices.recovery.concurrent_streams`::     See <<modules-indices>>`indices.recovery.file_chunk_size`::     See <<modules-indices>>`indices.recovery.translog_ops`::     See <<modules-indices>>`indices.recovery.translog_size`::     See <<modules-indices>>`indices.recovery.compress`::     See <<modules-indices>>`indices.recovery.max_bytes_per_sec`::     See <<modules-indices>>[float]==== Store level throttling`indices.store.throttle.type`::      See <<index-modules-store>>`indices.store.throttle.max_bytes_per_sec`::      See <<index-modules-store>>[float][[logger]]=== LoggerLogger values can also be updated by setting `logger.` prefix. Moresettings will be allowed to be updated.
 |