Skip to content

Commit 22701d2

Browse files
authored
Update manage-data/lifecycle/data-tiers.md
1 parent 60ecf0b commit 22701d2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

manage-data/lifecycle/data-tiers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -520,7 +520,7 @@ For example:
520520
},
521521
```
522522

523-
By defining the `migrate` action with `"enabled": false` for a data tier, this will [disable automatic ILM shard migration](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-migrate.md#ilm-disable-migrate-ex), for example, if you’re using the [allocate action](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-allocate.md) to manually specify allocation rules.
523+
Defining the `migrate` action with `"enabled": false` for a data tier [disables automatic {{ilm-init}} shard migration](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-migrate.md#ilm-disable-migrate-ex). This is useful if, for example, you’re using the [allocate action](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-allocate.md) to manually specify allocation rules.
524524

525525
#### Important Note:
526526
Do not disable automatic ILM migration without manually defining ILM allocation rules. If data migration is disabled without allocation rules defined, this can prevent data from moving to the specified data tier, although the data has successfully moved through the ILM policy with a status of `complete`.

0 commit comments

Comments
 (0)