From ffd86cb2ec3ee1ae6d90fdb6209e0a9f2540f5aa Mon Sep 17 00:00:00 2001 From: Maggie Ghamry <46542915+maggieghamry@users.noreply.github.com> Date: Wed, 17 Sep 2025 18:00:21 -0400 Subject: [PATCH 1/4] Update data-tiers.md The existing description of "automatic data tier migration" did not explicitly call out the impact of setting "migrate": { "enabled": false } without specifying manual allocation rules. The setting alone can prevent data from moving to a data tier while "succeeding" through the ILM "complete" phase. --- manage-data/lifecycle/data-tiers.md | 31 ++++++++++++++++++++++++++++- 1 file changed, 30 insertions(+), 1 deletion(-) diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index c888608896..30f938f130 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -494,4 +494,33 @@ This setting will not unallocate a currently allocated shard, but might prevent ### Automatic data tier migration [data-tier-migration] -{{ilm-init}} automatically transitions managed indices through the available data tiers using the [migrate](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-migrate.md) action. By default, this action is automatically injected in every phase. You can explicitly specify the migrate action with `"enabled": false` to [disable automatic 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. +{{ilm-init}} automatically transitions managed indices through the available data tiers using the [migrate](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-migrate.md) action. By default, this action is automatically injected in every phase. + +### Disable data tier allocation [data-tier-allocation] +You can explicitly disable data allocation for data tier migration in an ILM policy with the following setting: +```sh + "migrate": { + "enabled": false + } +``` + +For example: + +```sh + "cold": { + "min_age": "15m", + "actions": { + "set_priority": { + "priority": 0 + }, + "migrate": { + "enabled": false + } + } + }, +``` + +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. + +#### Important Note: +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`. From 60ecf0b51699cf4ccaf9ba83e87b531f6447d0ae Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Thu, 18 Sep 2025 13:23:55 -0400 Subject: [PATCH 2/4] Update manage-data/lifecycle/data-tiers.md --- manage-data/lifecycle/data-tiers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index 30f938f130..46e441f123 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -500,8 +500,8 @@ This setting will not unallocate a currently allocated shard, but might prevent You can explicitly disable data allocation for data tier migration in an ILM policy with the following setting: ```sh "migrate": { - "enabled": false - } + "enabled": false + } ``` For example: From 22701d241b9203a7f0efed67543dca37f99190a4 Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Thu, 18 Sep 2025 13:24:06 -0400 Subject: [PATCH 3/4] Update manage-data/lifecycle/data-tiers.md --- manage-data/lifecycle/data-tiers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index 46e441f123..4c37138b63 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -520,7 +520,7 @@ For example: }, ``` -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. +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. #### Important Note: 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`. From bfc09d2af9f46d7c47f184a267eccbbd7d0bffaf Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Thu, 18 Sep 2025 13:24:15 -0400 Subject: [PATCH 4/4] Update manage-data/lifecycle/data-tiers.md --- manage-data/lifecycle/data-tiers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index 4c37138b63..bddae9c1b3 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -523,4 +523,4 @@ For example: 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. #### Important Note: -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`. +Do not disable automatic {{ilm-init}} migration without manually defining {{ilm-init}} allocation rules. If data migration is disabled without allocation rules defined, this can prevent data from moving to the specified data tier, even though the data has successfully moved through the {{ilm-init}} policy with a status of `complete`.