data_tier_allocation.asciidoc 1.4 KB

1234567891011121314151617181920212223242526272829303132333435
  1. [role="xpack"]
  2. [[data-tier-shard-filtering]]
  3. === Index-level data tier allocation filtering
  4. You can use the index-level `_tier_preference` setting to control
  5. which <<data-tiers, data tier>> an index is allocated to.
  6. This setting corresponds to the data node roles:
  7. * <<data-content-node, data_content>>
  8. * <<data-hot-node, data_hot>>
  9. * <<data-warm-node, data_warm>>
  10. * <<data-cold-node, data_cold>>
  11. * <<data-frozen-node, data_frozen>>
  12. NOTE: The <<data-node, data>> role is not a valid data tier and cannot be used
  13. with the `_tier_preference` setting. The frozen tier stores <<partially-mounted,partially
  14. mounted indices>> exclusively.
  15. [discrete]
  16. [[data-tier-allocation-filters]]
  17. ==== Data tier allocation settings
  18. [[tier-preference-allocation-filter]]
  19. `index.routing.allocation.include._tier_preference`::
  20. Assign the index to the first tier in the list that has an available node.
  21. This prevents indices from remaining unallocated if no nodes are available
  22. in the preferred tier.
  23. For example, if you set `index.routing.allocation.include._tier_preference`
  24. to `data_warm,data_hot`, the index is allocated to the warm tier if there
  25. are nodes with the `data_warm` role. If there are no nodes in the warm tier,
  26. but there are nodes with the `data_hot` role, the index is allocated to
  27. the hot tier.
  28. Used in conjunction with <<data-tier-allocation,data tiers>>.