honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS]: ILM rollover max_age condition disregards origination date (#64404) (#64459) 

(cherry picked from commit d061c11899d6616b6d4356665b4a78a521bbc06f)
Signed-off-by: Andrei Dan <andrei.dan@elastic.co>
This commit is contained in:
Andrei Dan 2020-11-02 10:00:05 +00:00 committed by GitHub
parent 0a9481fcaf
commit dca1724bdc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/ilm/actions/ilm-rollover.asciidoc
View File

@ -49,8 +49,12 @@ You must specify at least one rollover condition.
An empty rollover action is invalid.
`max_age`::
(Optional, <<time-units, time units>>)
Triggers roll over after the maximum elapsed time from index creation is reached.
(Optional, <<time-units, time units>>)
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
<<index-lifecycle-parse-origination-date, index.lifecycle.parse_origination_date>> or
<<index-lifecycle-origination-date, index.lifecycle.origination_date>> settings)
`max_docs`::
(Optional, integer)

1
docs/reference/settings/ilm-settings.asciidoc
View File

@ -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`::
(<<indices-update-settings,Dynamic>>, Boolean)
Set to `true` to parse the origination date from the index name.