honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Tidied up cluster settings docs

This commit is contained in:
Clinton Gormley 2014-01-15 14:51:18 +01:00
parent f8a427e266
commit a0b993e2dc
1 changed files with 26 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/reference/modules/cluster.asciidoc
View File

@ -35,38 +35,25 @@ The following settings may be used:
How many concurrent recoveries are allowed to happen on a node. How many concurrent recoveries are allowed to happen on a node.
Defaults to `2`. Defaults to `2`.
added[1.0.0.RC1]
`cluster.routing.allocation.enable`:: `cluster.routing.allocation.enable`::
Controls shard allocation for all indices, by allowing specific Controls shard allocation for all indices, by allowing specific
kinds of shard to be allocated. Can be set to: kinds of shard to be allocated.
added[1.0.0.RC1,Replaces `cluster.routing.allocation.disable*`]
Can be set to:
* `all` (default) - Allows shard allocation for all kinds of shards. * `all` (default) - Allows shard allocation for all kinds of shards.
* `primaries` - Allows shard allocation only for primary shards. * `primaries` - Allows shard allocation only for primary shards.
* `new_primaries` - Allows shard allocation only for primary shards for new indices. * `new_primaries` - Allows shard allocation only for primary shards for new indices.
* `none` - No shard allocations of any kind are allowed for all indices. * `none` - No shard allocations of any kind are allowed for all indices.
`cluster.routing.allocation.disable_new_allocation`:: `cluster.routing.allocation.disable_new_allocation`::
Allows to disable new primary allocations. Note, this will prevent deprecated[1.0.0.RC1,Replaced by `cluster.routing.allocation.enable`]
allocations for newly created indices. This setting really make
sense when dynamically updating it using the cluster update
settings API. This setting has been deprecated in favour
for `cluster.routing.allocation.enable`.
`cluster.routing.allocation.disable_allocation`:: `cluster.routing.allocation.disable_allocation`::
Allows to disable either primary or replica allocation (does not deprecated[1.0.0.RC1,Replaced by `cluster.routing.allocation.enable`]
apply to newly created primaries, see `disable_new_allocation`
above). Note, a replica will still be promoted to primary if
one does not exist. This setting really make sense when
dynamically updating it using the cluster update settings API.
This setting has been deprecated in favour for `cluster.routing.allocation.enable`.
`cluster.routing.allocation.disable_replica_allocation`:: `cluster.routing.allocation.disable_replica_allocation`::
Allows to disable only replica allocation. Similar to the previous deprecated[1.0.0.RC1,Replaced by `cluster.routing.allocation.enable`]
setting, mainly make sense when using it dynamically using the
cluster update settings API. This setting has been deprecated in
favour for `cluster.routing.allocation.enable`.
`cluster.routing.allocation.same_shard.host`:: `cluster.routing.allocation.same_shard.host`::
Prevents that multiple instances of the same shard are allocated Prevents that multiple instances of the same shard are allocated