From dca1724bdce98ee8173954bb0dda59e03415029f Mon Sep 17 00:00:00 2001 From: Andrei Dan Date: Mon, 2 Nov 2020 10:00:05 +0000 Subject: [PATCH] [DOCS]: ILM rollover max_age condition disregards origination date (#64404) (#64459) (cherry picked from commit d061c11899d6616b6d4356665b4a78a521bbc06f) Signed-off-by: Andrei Dan --- docs/reference/ilm/actions/ilm-rollover.asciidoc | 8 ++++++-- docs/reference/settings/ilm-settings.asciidoc | 1 + 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/reference/ilm/actions/ilm-rollover.asciidoc b/docs/reference/ilm/actions/ilm-rollover.asciidoc index 8b84d50cd62..42d4d47f67a 100644 --- a/docs/reference/ilm/actions/ilm-rollover.asciidoc +++ b/docs/reference/ilm/actions/ilm-rollover.asciidoc @@ -49,8 +49,12 @@ You must specify at least one rollover condition. An empty rollover action is invalid. `max_age`:: -(Optional, <>) -Triggers roll over after the maximum elapsed time from index creation is reached. +(Optional, <>) +Triggers roll over after the maximum elapsed time from index creation is reached. +The elapsed time is always calculated since the index creation time, even if the +index origination date is configured to a custom date (via the +<> or +<> settings) `max_docs`:: (Optional, integer) diff --git a/docs/reference/settings/ilm-settings.asciidoc b/docs/reference/settings/ilm-settings.asciidoc index e94dc98b357..6aa79df9ec1 100644 --- a/docs/reference/settings/ilm-settings.asciidoc +++ b/docs/reference/settings/ilm-settings.asciidoc @@ -48,6 +48,7 @@ Use this setting if you create a new index that contains old data and want to use the original creation date to calculate the index age. Specified as a Unix epoch value. +[[index-lifecycle-parse-origination-date]] `index.lifecycle.parse_origination_date`:: (<>, Boolean) Set to `true` to parse the origination date from the index name.