Skip to content

Commit e427a97

Browse files
Super small changes to apply/policy pages (#2923)
Edu noted that these two pages seem a bit similar, so I'm adding a sentence or two to each to help clarify the scope. Also, the title change is just for better consistency in the navigation pane. Preview: - [Manually apply a lifecycle policy to an index](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2923/manage-data/lifecycle/index-lifecycle-management/policy-apply) - [Update or switch a lifecycle policy](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2923/manage-data/lifecycle/index-lifecycle-management/policy-updates) Rel: elastic/docs-content-internal#190 --------- Co-authored-by: wajihaparvez <[email protected]>
1 parent cd9745a commit e427a97

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

manage-data/lifecycle/index-lifecycle-management/policy-apply.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,20 +8,21 @@ products:
88

99
# Manually apply a lifecycle policy to an index [apply-policy-manually]
1010

11-
When you create a new {{es}} index, it automatically picks up settings, mappings, and aliases from any matching [index template](/manage-data/data-store/templates.md#index-templates) and its component templates. If the template specifies a lifecycle policy, that policy is applied to the new index as soon as it's created. This process is described in detail in [Configure a lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md).
11+
When you create a new {{es}} index, it automatically picks up settings, mappings, and aliases from any matching [index template](/manage-data/data-store/templates.md#index-templates) and its component templates. If the template specifies a lifecycle policy, that policy is applied to the new index as soon as it's created so that the index will be managed by {{ilm-init}}. This process is described in detail in [Configure a lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md).
1212

13-
You can also apply a lifecycle policy manually to existing indices, as described on this page. This is useful if you want to:
13+
You can also apply a lifecycle policy manually to existing indices that are not yet managed, as described on this page. This is useful if you want to:
1414
* Configure the indices to move through different [data tiers](/manage-data/lifecycle/data-tiers.md) as they age.
1515
* Perform [lifecycle actions](elasticsearch://reference/elasticsearch/index-lifecycle-actions/index.md) such as downsampling or shrinking.
1616
* Delete the indices when they reach a certain age.
1717

18-
If an index is currently managed by an ILM policy you must first remove that policy before applying a new one. Refer to [Switch to a different lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/policy-updates.md#switch-lifecycle-policies) for details.
18+
:::{warning}
19+
Consider the following before manually applying a policy to an index:
1920

20-
You can do this procedure in {{kib}} or using the {{es}} API.
21+
* If an index is currently managed by an ILM policy you must first remove that policy before applying a new one. To remove or make changes to an {{ilm-init}} policy currently applied to one or more indices, or to switch indices to use a different policy, refer to [Update or switch a lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/policy-updates.md).
22+
* Do not manually apply a policy that uses the rollover action. Policies that use rollover must be applied by the [index template](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md#apply-policy-template). Otherwise, the policy is not carried forward when the rollover action creates a new index.
23+
:::
2124

22-
::::{warning}
23-
Do not manually apply a policy that uses the rollover action. Policies that use rollover must be applied by the [index template](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md#apply-policy-template). Otherwise, the policy is not carried forward when the rollover action creates a new index.
24-
::::
25+
You can do this procedure in {{kib}} or using the {{es}} API.
2526

2627
::::{tab-set}
2728
:group: kibana-api

manage-data/lifecycle/index-lifecycle-management/policy-updates.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
---
2-
navigation_title: Update or switch a policy
32
mapped_pages:
43
- https://www.elastic.co/guide/en/elasticsearch/reference/current/update-lifecycle-policy.html
54
applies_to:
@@ -10,13 +9,13 @@ products:
109

1110
# Update or switch a lifecycle policy
1211

13-
1412
You can change how the lifecycle of an index or collection of rolling indices is managed by modifying the current policy or switching to a different policy.
1513

1614
To ensure that policy updates don’t put an index into a state where it can’t exit the current phase, the phase definition is cached in the index metadata when it enters the phase. If changes can be safely applied, {{ilm-init}} updates the cached phase definition. If they cannot, phase execution continues using the cached definition.
1715

1816
When the index advances to the next phase, it uses the phase definition from the updated policy.
1917

18+
To configure an index not currently managed by {{ilm-init}} to be governed by an lifecycle policy, refer to [Manually apply a policy to an index](/manage-data/lifecycle/index-lifecycle-management/policy-apply.md).
2019

2120
## How changes are applied [ilm-apply-changes]
2221

0 commit comments

Comments
 (0)