honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-25 17:38:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document all shard allocation filtering attributes (#46992)

Browse Source 
This commit adds coverage to the docs for some missing built-in shard
allocation attributes.
This commit is contained in:
weizijun 2019-11-21 21:29:45 +08:00 committed by Jason Tedor
parent d59ea64ccd
commit 3eb577f6c8
No known key found for this signature in database
GPG Key ID: FA89F05560F16BC5
2 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/reference/index-modules/allocation/filtering.asciidoc
View File

@ -7,7 +7,7 @@ a particular index. These per-index filters are applied in conjunction with
<<allocation-awareness, allocation awareness>>. <<allocation-awareness, allocation awareness>>.
Shard allocation filters can be based on custom node attributes or the built-in Shard allocation filters can be based on custom node attributes or the built-in
`_name`, `host_ip`, `publish_ip`, `_ip`, and `_host` attributes. `_name`, `_host_ip`, `_publish_ip`, `_ip`, `_host` and `_id` attributes.
<<index-lifecycle-management, Index lifecycle management>> uses filters based <<index-lifecycle-management, Index lifecycle management>> uses filters based
on custom node attributes to determine how to reallocate shards when moving on custom node attributes to determine how to reallocate shards when moving
between phases. between phases.
@ -101,6 +101,7 @@ The index allocation settings support the following built-in attributes:
`_publish_ip`:: Match nodes by publish IP address `_publish_ip`:: Match nodes by publish IP address
`_ip`:: Match either `_host_ip` or `_publish_ip` `_ip`:: Match either `_host_ip` or `_publish_ip`
`_host`:: Match nodes by hostname `_host`:: Match nodes by hostname
`_id`:: Match nodes by node id
You can use wildcards when specifying attribute values, for example: You can use wildcards when specifying attribute values, for example:

13
docs/reference/modules/cluster/allocation_filtering.asciidoc
View File

@ -7,7 +7,7 @@ conjunction with <<shard-allocation-filtering, per-index allocation filtering>>
and <<allocation-awareness, allocation awareness>>. and <<allocation-awareness, allocation awareness>>.
Shard allocation filters can be based on custom node attributes or the built-in Shard allocation filters can be based on custom node attributes or the built-in
`_name`, `_ip`, and `_host` attributes. `_name`, `_host_ip`, `_publish_ip`, `_ip`, `_host` and `_id` attributes.
The `cluster.routing.allocation` settings are dynamic, enabling live indices to The `cluster.routing.allocation` settings are dynamic, enabling live indices to
be moved from one set of nodes to another. Shards are only relocated if it is be moved from one set of nodes to another. Shards are only relocated if it is
@ -50,9 +50,14 @@ PUT _cluster/settings
The cluster allocation settings support the following built-in attributes: The cluster allocation settings support the following built-in attributes:
[horizontal] [horizontal]
`_name`:: Match nodes by node names `_name`:: Match nodes by node name
`_ip`:: Match nodes by IP addresses (the IP address associated with the hostname) `_host_ip`:: Match nodes by host IP address (IP associated with hostname)
`_host`:: Match nodes by hostnames `_publish_ip`:: Match nodes by publish IP address
`_ip`:: Match either `_host_ip` or `_publish_ip`
`_host`:: Match nodes by hostname
`_id`:: Match nodes by node id
You can use wildcards when specifying attribute values, for example: You can use wildcards when specifying attribute values, for example: