mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
33a71e3289
* Remove `es-test-dir` book-scoped variable * Remove `plugins-examples-dir` book-scoped variable * Remove `:dependencies-dir:` and `:xes-repo-dir:` book-scoped variables - In `index.asciidoc`, two variables (`:dependencies-dir:` and `:xes-repo-dir:`) were removed. - In `sql/index.asciidoc`, the `:sql-tests:` path was updated to fuller path - In `esql/index.asciidoc`, the `:esql-tests:` path was updated idem * Replace `es-repo-dir` with `es-ref-dir` * Move `:include-xpack: true` to few files that use it, remove from index.asciidoc
18 lines
827 B
Text
18 lines
827 B
Text
[[troubleshoot-migrate-to-tiers]]
|
|
== Indices mix index allocation filters with data tiers node roles to move through data tiers
|
|
|
|
Elasticsearch standardized the implementation of https://www.elastic.co/blog/elasticsearch-data-lifecycle-management-with-data-tiers[hot-warm-cold architectures]
|
|
to <<data-tiers, data tiers>> in version 7.10.
|
|
Some indices and deployments might have not fully transitioned to <<data-tiers, data tiers>>
|
|
and mix the new way of implementing the hot-warm-cold architecture with
|
|
<<shard-allocation-filtering, legacy>> based node attributes.
|
|
|
|
This could lead to unassigned shards or shards not transitioning to the desired
|
|
<<data-tiers, tier>>.
|
|
|
|
In order to fix this follow the next steps:
|
|
|
|
include::{es-ref-dir}/tab-widgets/troubleshooting/data/migrate-to-data-tiers-routing-guide-widget.asciidoc[]
|
|
|
|
|
|
|