IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

› › ›

Index-level data tier allocation filtering

edit

Index-level data tier allocation filtering

edit

You can use index-level allocation settings to control which data tier the index is allocated to. The data tier allocator is a shard allocation filter that uses two built-in node attributes: _tier and _tier_preference.

These tier attributes are set using the data node roles:

The data role is not a valid data tier and cannot be used for data tier filtering. The data_frozen role can only be used for searchable snapshots mounted with the shared_cache option.

Data tier allocation settings

edit

index.routing.allocation.include._tier: Assign the index to a node whose node.roles configuration has at least one of to the comma-separated values.
index.routing.allocation.require._tier: Assign the index to a node whose node.roles configuration has all of the comma-separated values.
index.routing.allocation.exclude._tier: Assign the index to a node whose node.roles configuration has none of the comma-separated values.

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.

« Total shards per node Index blocks »