[[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] -------------------------------------------------- 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 the last 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 <>. `cluster.routing.allocation.awareness.force.*`:: See <>. [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 <>. [float] ===== Disable allocation added[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 <>. `cluster.routing.allocation.disable_replica_allocation`:: See <>. `cluster.routing.allocation.disable_new_allocation`:: See <>. [float] ===== Enable allocation `cluster.routing.allocation.enable`:: See <>. [float] ===== Throttling allocation `cluster.routing.allocation.node_initial_primaries_recoveries`:: See <>. `cluster.routing.allocation.node_concurrent_recoveries`:: See <>. [float] ===== Filter allocation `cluster.routing.allocation.include.*`:: See <>. `cluster.routing.allocation.exclude.*`:: See <>. `cluster.routing.allocation.require.*` See <>. [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 <> `discovery.zen.publish_timeout` coming[1.1.0, The setting existed before but wasn't dynamic]:: See <> [float] ==== Threadpools `threadpool.*`:: See <> [float] [[cluster-index-settings]] === Index settings [float] ==== Index filter cache `indices.cache.filter.size`:: See <> `indices.cache.filter.expire` (time):: See <> [float] ==== TTL interval `indices.ttl.interval` (time):: See <> [float] ==== Recovery `indices.recovery.concurrent_streams`:: See <> `indices.recovery.file_chunk_size`:: See <> `indices.recovery.translog_ops`:: See <> `indices.recovery.translog_size`:: See <> `indices.recovery.compress`:: See <> `indices.recovery.max_bytes_per_sec`:: See <> [float] ==== Store level throttling `indices.store.throttle.type`:: See <> `indices.store.throttle.max_bytes_per_sec`:: See <> [float] [[logger]] === Logger Logger values can also be updated by setting `logger.` prefix. More settings will be allowed to be updated.