From 05bb66ab0828c02148f20c6d2e39e6960916d9e9 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Tue, 21 Oct 2025 16:39:11 +0100 Subject: [PATCH] Fix link to the conceptual page about rollover When working on #1553, I've noticed that this troubleshooting section link was pointing to the wrong page. The Rollover page in the Manage data docs used to have a section about automating rollover with ILM, so I imagine this is trying to point to the info on that page. --- troubleshoot/elasticsearch/index-lifecycle-management-errors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/troubleshoot/elasticsearch/index-lifecycle-management-errors.md b/troubleshoot/elasticsearch/index-lifecycle-management-errors.md index 4890292942..0b15af6617 100644 --- a/troubleshoot/elasticsearch/index-lifecycle-management-errors.md +++ b/troubleshoot/elasticsearch/index-lifecycle-management-errors.md @@ -151,7 +151,7 @@ POST /my-index-000001/_ilm/retry ### How `min_age` is calculated [min-age-calculation] -When setting up an [{{ilm-init}} policy](../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) or [automating rollover with {{ilm-init}}](../../manage-data/lifecycle/index-lifecycle-management.md), be aware that `min_age` can be relative to either the rollover time or the index creation time. +When setting up an [{{ilm-init}} policy](../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) or [automating rollover with {{ilm-init}}](../../manage-data/lifecycle/index-lifecycle-management/rollover.md), be aware that `min_age` can be relative to either the rollover time or the index creation time. If you use [{{ilm-init}} rollover](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-rollover.md), `min_age` is calculated relative to the time the index was rolled over. This is because the [rollover API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-rollover) generates a new index and updates the `age` of the previous index to reflect the rollover time. If the index hasn’t been rolled over, then the `age` is the same as the `creation_date` for the index.