Skip rollover

Stack

You can use index lifecycle management 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 policy to automatically move indices through lifecycle phases 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 policy or manually by adjusting the index settings.

When you configure a lifecycle policy in Kibana, you can choose whether or not rollover is enabled.

To update the automatic rollover setting in an ILM policy:

1. Go to Stack Management > Index Lifecycle Policies.

2. Select a policy to update, and from the Actions menu select Edit.

3. In the Hot phase section, expand the advanced settings.

4. Update the Enable rollover option to enable or disable automatic rollover.

   

When the index.lifecycle.indexing_complete setting is true, ILM 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 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 to continue to manage the index. If you use the rollover API rather than an ILM 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.

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.
2. Bootstrap the initial index.
3. Change the write index for the alias to the bootstrapped index using the aliases API.
4. Set index.lifecycle.indexing_complete to true on the old index to indicate that it does not need to be rolled over.

ILM continues to manage the old index in accordance with your existing policy. New indices are named according to the new template and managed according to the same policy without interruption.