From 0cefc293d0b0750eca3af24c311a5688fb751524 Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Fri, 3 Oct 2025 13:15:08 -0400 Subject: [PATCH 1/3] ILM docs: Update 'Skip rollover' --- .../skip-rollover.md | 31 ++++++++++++++++--- 1 file changed, 27 insertions(+), 4 deletions(-) diff --git a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md index e2c1b3fe75..a0def7949d 100644 --- a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md +++ b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md @@ -9,17 +9,40 @@ products: # Skip rollover [skipping-rollover] -When `index.lifecycle.indexing_complete` is set to `true`, {{ilm-init}} won’t perform the rollover action on an index, even if it otherwise meets the rollover criteria. It’s set automatically by {{ilm-init}} when the rollover action completes successfully. +You may want to use {{ilm}} to manage your indices but do not want your indices to roll over automatically. For instance, if you're not working with continuously ingested data, you may prefer to create a new index on a regular interval, such as the first Monday of each month. In this case you may not want your indices to roll over, but you do still want to use an {{ilm-init}} policy to have the indices transition automatically through [lifecycle phases](/manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md#ilm-phase-transitions) as they age. -You can set it manually to skip rollover if you need to make an exception to your normal lifecycle policy and update the alias to force a roll over, but want {{ilm-init}} to continue to manage the index. If you use the rollover API, it is not necessary to configure this setting manually. +You can configure indices to skip rollover either as part of an {{ilm-init}} policy or manually by adjusting the index settings. + + +## Skip rollover through an {{ilm-init}} policy + +When you [configure a lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) in {{kib}}, you can choose whether or not rollover is enabled. + +To update the automatic rollover setting in an {{ilm-init}} policy: + +1. Go to **Stack Management > Index Lifecycle Policies**. + +1. Select a policy to update, and from the **Actions** menu select **Edit**. + +1. In the **Hot phase** section, expand the advanced settings. + +1. Update the **Enable rollover** option to enable or disable automatic rollover. + + ![Create policy page](/manage-data/images/elasticsearch-reference-create-policy.png "") + + +## Skip rollover manually + +When the [`index.lifecycle.indexing_complete`](elasticsearch://reference/elasticsearch/configuration-reference/index-lifecycle-management-settings.md#_index_level_settings_2) setting is `true`, {{ilm-init}} won’t perform the rollover action on an index, even if it otherwise meets the rollover criteria. This setting is updated to `true` automatically by {{ilm-init}} when the rollover action completes successfully. + +You can update this setting manually to skip rollover if, for instance, you need to make an exception to your normal lifecycle policy and update the alias to force a rollover, but you want {{ilm-init}} to continue to manage the index. If you use the rollover API rather than an {{ilm-init}} policy to rollover indices, it is not necessary to configure this setting manually. If an index’s lifecycle policy is removed, this setting is also removed. ::::{important} -When `index.lifecycle.indexing_complete` is `true`, {{ilm-init}} verifies that the index is no longer the write index for the alias specified by `index.lifecycle.rollover_alias`. If the index is still the write index or the rollover alias is not set, the index is moved to the [`ERROR` step](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md). +When `index.lifecycle.indexing_complete` is set to `true`, {{ilm-init}} verifies that the index is no longer the write index for the alias specified by `index.lifecycle.rollover_alias`. If the index is still the write index or the rollover alias is not set, the index is moved to the [`ERROR` step](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md). :::: - For example, if you need to change the name of new indices in a series while retaining previously-indexed data in accordance with your configured policy, you can: 1. Create a template for the new index pattern that uses the same policy. From 92099da1c9152e40277f32d4a4895559190a7b48 Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Mon, 6 Oct 2025 12:33:22 -0400 Subject: [PATCH 2/3] Update manage-data/lifecycle/index-lifecycle-management/skip-rollover.md Co-authored-by: Vlada Chirmicci --- .../lifecycle/index-lifecycle-management/skip-rollover.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md index a0def7949d..fae1602ea2 100644 --- a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md +++ b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md @@ -9,7 +9,7 @@ products: # Skip rollover [skipping-rollover] -You may want to use {{ilm}} to manage your indices but do not want your indices to roll over automatically. For instance, if you're not working with continuously ingested data, you may prefer to create a new index on a regular interval, such as the first Monday of each month. In this case you may not want your indices to roll over, but you do still want to use an {{ilm-init}} policy to have the indices transition automatically through [lifecycle phases](/manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md#ilm-phase-transitions) as they age. +You can use {{ilm}} to manage index lifecycle transitions without rolling over your indices. For example, when working with data that isn't continuously ingested, you might prefer to create a new index on a set schedule, such as the first Monday of each month. In this case, you can still use an {{ilm-init}} policy to automatically move indices through [lifecycle phases](/manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md#ilm-phase-transitions) as they age and control when new indices are created by disabling the rollover action. You can configure indices to skip rollover either as part of an {{ilm-init}} policy or manually by adjusting the index settings. From 0c6ed0f7488450cc19ce63370eafbc65917a6164 Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Mon, 6 Oct 2025 12:33:34 -0400 Subject: [PATCH 3/3] Update manage-data/lifecycle/index-lifecycle-management/skip-rollover.md Co-authored-by: Vlada Chirmicci --- .../lifecycle/index-lifecycle-management/skip-rollover.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md index fae1602ea2..b2bfd8d5fd 100644 --- a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md +++ b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md @@ -35,7 +35,7 @@ To update the automatic rollover setting in an {{ilm-init}} policy: When the [`index.lifecycle.indexing_complete`](elasticsearch://reference/elasticsearch/configuration-reference/index-lifecycle-management-settings.md#_index_level_settings_2) setting is `true`, {{ilm-init}} won’t perform the rollover action on an index, even if it otherwise meets the rollover criteria. This setting is updated to `true` automatically by {{ilm-init}} when the rollover action completes successfully. -You can update this setting manually to skip rollover if, for instance, you need to make an exception to your normal lifecycle policy and update the alias to force a rollover, but you want {{ilm-init}} to continue to manage the index. If you use the rollover API rather than an {{ilm-init}} policy to rollover indices, it is not necessary to configure this setting manually. +You can update this setting manually to skip rollover if, for instance, you need to make an exception to your normal lifecycle policy and update the alias to force a rollover, but you want {{ilm-init}} to continue to manage the index. If you use the rollover API rather than an {{ilm-init}} policy to roll over indices, it is not necessary to configure this setting manually. If an index’s lifecycle policy is removed, this setting is also removed.