Skip to content

Commit 38d5939

Browse files
authored
Merge branch 'main' into 190/tutorials-move
2 parents d7beeae + 1b508da commit 38d5939

File tree

2 files changed

+36
-2
lines changed

2 files changed

+36
-2
lines changed

manage-data/lifecycle/data-tiers.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -494,4 +494,33 @@ This setting will not unallocate a currently allocated shard, but might prevent
494494

495495
### Automatic data tier migration [data-tier-migration]
496496

497-
{{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.
497+
{{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.
498+
499+
### Disable data tier allocation [data-tier-allocation]
500+
You can explicitly disable data allocation for data tier migration in an ILM policy with the following setting:
501+
```sh
502+
"migrate": {
503+
"enabled": false
504+
}
505+
```
506+
507+
For example:
508+
509+
```sh
510+
"cold": {
511+
"min_age": "15m",
512+
"actions": {
513+
"set_priority": {
514+
"priority": 0
515+
},
516+
"migrate": {
517+
"enabled": false
518+
}
519+
}
520+
},
521+
```
522+
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.
524+
525+
#### Important Note:
526+
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`.

redirects.yml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -358,4 +358,9 @@ redirects:
358358
'solutions/search/serverless-elasticsearch-get-started.md': 'solutions/search/get-started.md'
359359

360360
# Related to https://github.com/elastic/docs-content/pull/3032
361-
'manage-data/lifecycle/index-lifecycle-management/tutorial-automate-rollover.md': 'manage-data/lifecycle/index-lifecycle-management/ilm-tutorials.md'
361+
'manage-data/lifecycle/index-lifecycle-management/tutorial-automate-rollover.md': 'manage-data/lifecycle/index-lifecycle-management/ilm-tutorials.md'
362+
363+
# Remove duplicate reference content
364+
'deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md': 'elasticsearch://reference/elasticsearch/roles.md'
365+
'deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md': 'elasticsearch://reference/elasticsearch/security-privileges.md'
366+

0 commit comments

Comments
 (0)