mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
95bccda599
These settings were deprecated in 7.13+ in #72835 and are now removed by this commit. This commit also ensures that the settings are removed from index metadata when the metadata is loaded. The reason for this is that if we allow the settings to remain (because they are not technically "invalid"), then the index will not be able to be allocated, because the FilterAllocationDecider will be looking for nodes with the _tier attribute.
36 lines
1.4 KiB
Text
36 lines
1.4 KiB
Text
[role="xpack"]
|
|
[[data-tier-shard-filtering]]
|
|
=== Index-level data tier allocation filtering
|
|
|
|
You can use index-level allocation settings to control which <<data-tiers, data tier>>
|
|
the index is allocated to. The data tier allocator is a
|
|
<<shard-allocation-filtering, shard allocation filter>> that uses two built-in
|
|
node attributes: `_tier` and `_tier_preference`.
|
|
|
|
These tier attributes are set using the data node roles:
|
|
|
|
* <<data-content-node, data_content>>
|
|
* <<data-hot-node, data_hot>>
|
|
* <<data-warm-node, data_warm>>
|
|
* <<data-cold-node, data_cold>>
|
|
* <<data-frozen-node, data_frozen>>
|
|
|
|
NOTE: The <<data-node, data>> role is not a valid data tier and cannot be used
|
|
for data tier filtering. The frozen tier stores <<partially-mounted,partially
|
|
mounted indices>> exclusively.
|
|
|
|
[discrete]
|
|
[[data-tier-allocation-filters]]
|
|
==== Data tier allocation settings
|
|
|
|
[[tier-preference-allocation-filter]]
|
|
`index.routing.allocation.include._tier_preference`::
|
|
|
|
Assign the index to the first tier in the list that has an available node.
|
|
This prevents indices from remaining unallocated if no nodes are available
|
|
in the preferred tier.
|
|
For example, if you set `index.routing.allocation.include._tier_preference`
|
|
to `data_warm,data_hot`, the index is allocated to the warm tier if there
|
|
are nodes with the `data_warm` role. If there are no nodes in the warm tier,
|
|
but there are nodes with the `data_hot` role, the index is allocated to
|
|
the hot tier.
|