› › ›

Index-level data tier allocation filtering

You can use the index-level _tier_preference setting to control which data tier an index is allocated to.

This setting corresponds to the data node roles:

The data role is not a valid data tier and cannot be used with the _tier_preference setting. The frozen tier stores partially mounted indices exclusively.

Data tier allocation settings

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. Used in conjunction with data tiers.

© 2023-2025 Elasticsearch
As of September 2024, Elasticsearch is available under a choice of three licenses: the Server Side Public License (SSPL), the Elastic License, or the AGPLv3 (OSI approved).
Elasticsearch and the Elasticsearch logo are trademarks of Elasticsearch B.V., registered in the U.S. and in other countries.
https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-tier-shard-filtering.html