From 72a9367275fe165c14618e233930d9fcdf178dd7 Mon Sep 17 00:00:00 2001 From: Joe Gallo Date: Mon, 6 Dec 2021 14:29:13 -0500 Subject: [PATCH 1/6] We ignore nulls here now --- docs/reference/datatiers.asciidoc | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/reference/datatiers.asciidoc b/docs/reference/datatiers.asciidoc index 5bb3c4f755283..104dca5e6961a 100644 --- a/docs/reference/datatiers.asciidoc +++ b/docs/reference/datatiers.asciidoc @@ -118,7 +118,6 @@ settings in the create index request or index template that matches the new inde You can also explicitly set `index.routing.allocation.include._tier_preference` to opt out of the default tier-based allocation. -If you set the tier preference to `null`, {es} ignores the data tier roles during allocation. [discrete] [[data-tier-migration]] From 78d2d5dee074f06be4c3622ef4b8fcbc6178a147 Mon Sep 17 00:00:00 2001 From: Joe Gallo Date: Mon, 6 Dec 2021 14:29:30 -0500 Subject: [PATCH 2/6] Shard allocation filtering doesn't affect this either --- docs/reference/datatiers.asciidoc | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/reference/datatiers.asciidoc b/docs/reference/datatiers.asciidoc index 104dca5e6961a..b83f02e81c0d3 100644 --- a/docs/reference/datatiers.asciidoc +++ b/docs/reference/datatiers.asciidoc @@ -112,10 +112,6 @@ by default {es} sets <> to `data_hot` to automatically allocate the index shards to the hot tier. -You can override the automatic tier-based allocation by specifying -<> -settings in the create index request or index template that matches the new index. - You can also explicitly set `index.routing.allocation.include._tier_preference` to opt out of the default tier-based allocation. From 4f47879117d2e3bf3637bf8a745801a765111246 Mon Sep 17 00:00:00 2001 From: Joe Gallo Date: Mon, 6 Dec 2021 15:03:24 -0500 Subject: [PATCH 3/6] Drop remaining vestigial _tier documentation and rewrite the page slightly -- there's only _tier_preference so we don't have to talk about 'settings' or 'attributes', it's just the one. --- .../allocation/data_tier_allocation.asciidoc | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/reference/index-modules/allocation/data_tier_allocation.asciidoc b/docs/reference/index-modules/allocation/data_tier_allocation.asciidoc index 732f8edc5b0a8..44d702c49c9af 100644 --- a/docs/reference/index-modules/allocation/data_tier_allocation.asciidoc +++ b/docs/reference/index-modules/allocation/data_tier_allocation.asciidoc @@ -2,12 +2,10 @@ [[data-tier-shard-filtering]] === Index-level data tier allocation filtering -You can use index-level allocation settings to control which <> -the index is allocated to. The data tier allocator is a -<> that uses two built-in -node attributes: `_tier` and `_tier_preference`. +You can use the index-level `_tier_preference` setting to control +which <> an index is allocated to. -These tier attributes are set using the data node roles: +This setting corresponds to the data node roles: * <> * <> @@ -16,7 +14,7 @@ These tier attributes are set using the data node roles: * <> NOTE: The <> role is not a valid data tier and cannot be used -for data tier filtering. The frozen tier stores <> exclusively. [discrete] @@ -34,3 +32,4 @@ mounted indices>> exclusively. 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 conjuction with <>. From 0f882e05d716bf1d41390438f94a8092dcba0fb6 Mon Sep 17 00:00:00 2001 From: Joe Gallo Date: Mon, 6 Dec 2021 15:14:44 -0500 Subject: [PATCH 4/6] We always inject the migrate action So reword this section to more strongly indicate that you'll need to disable it if you don't want it -- it's not enough to 'merely' specify some manual allocation. --- docs/reference/datatiers.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/reference/datatiers.asciidoc b/docs/reference/datatiers.asciidoc index b83f02e81c0d3..a8663bae2e839 100644 --- a/docs/reference/datatiers.asciidoc +++ b/docs/reference/datatiers.asciidoc @@ -122,5 +122,6 @@ to opt out of the default tier-based allocation. {ilm-init} automatically transitions managed indices through the available data tiers using the <> action. By default, this action is automatically injected in every phase. -You can explicitly specify the migrate action to override the default behavior, -or use the <> to manually specify allocation rules. +You can explicitly specify the migrate action to disable automatic migration, +for example, if you're using the <> to manually +specify allocation rules. From 49a05b68bec9d1b2d142ae55b02359d9342f55bc Mon Sep 17 00:00:00 2001 From: Joe Gallo Date: Mon, 6 Dec 2021 15:44:50 -0500 Subject: [PATCH 5/6] Reword slightly 'also' made more sense before the preceding paragraph was removed. --- docs/reference/datatiers.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/datatiers.asciidoc b/docs/reference/datatiers.asciidoc index a8663bae2e839..b6d0e736ced79 100644 --- a/docs/reference/datatiers.asciidoc +++ b/docs/reference/datatiers.asciidoc @@ -112,7 +112,7 @@ by default {es} sets <> to `data_hot` to automatically allocate the index shards to the hot tier. -You can also explicitly set `index.routing.allocation.include._tier_preference` +You can explicitly set `index.routing.allocation.include._tier_preference` to opt out of the default tier-based allocation. [discrete] From f61533c53e6ebbe4e11c1ff2f5d34a7ec99b39df Mon Sep 17 00:00:00 2001 From: Joe Gallo Date: Mon, 6 Dec 2021 17:48:10 -0500 Subject: [PATCH 6/6] Mention "enabled": false --- docs/reference/datatiers.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/datatiers.asciidoc b/docs/reference/datatiers.asciidoc index b6d0e736ced79..00e6daeec2892 100644 --- a/docs/reference/datatiers.asciidoc +++ b/docs/reference/datatiers.asciidoc @@ -122,6 +122,6 @@ to opt out of the default tier-based allocation. {ilm-init} automatically transitions managed indices through the available data tiers using the <> action. By default, this action is automatically injected in every phase. -You can explicitly specify the migrate action to disable automatic migration, +You can explicitly specify the migrate action with `"enabled": false` to disable automatic migration, for example, if you're using the <> to manually specify allocation rules.