2019-04-05 19:38:31 -04:00
|
|
|
[role="xpack"]
|
|
|
|
|
[[ilm-settings]]
|
|
|
|
|
=== {ilm-cap} settings
|
|
|
|
|
|
|
|
|
|
These index-level {ilm-init} settings are typically configured through index
|
|
|
|
|
templates. For more information, see <<ilm-gs-create-policy>>.
|
|
|
|
|
|
|
|
|
|
`index.lifecycle.name`::
|
|
|
|
|
The name of the policy to use to manage the index.
|
|
|
|
|
|
|
|
|
|
`index.lifecycle.rollover_alias`::
|
|
|
|
|
The index alias to update when the index rolls over. Specify when using a
|
|
|
|
|
policy that contains a rollover action. When the index rolls over, the alias is
|
|
|
|
|
updated to reflect that the index is no longer the write index. For more
|
|
|
|
|
information about rollover, see <<using-policies-rollover>>.
|
2019-08-20 12:58:57 -04:00
|
|
|
|
|
|
|
|
`indices.lifecycle.poll_interval`::
|
|
|
|
|
(<<time-units, time units>>) How often {ilm} checks for indices that meet policy
|
|
|
|
|
criteria. Defaults to `10m`.
|
2019-09-16 03:50:28 -04:00
|
|
|
|
|
|
|
|
`index.lifecycle.origination_date`::
|
|
|
|
|
The timestamp that will be used to calculate the index age for its phase
|
|
|
|
|
transitions. This allows the users to create an index containing old data and
|
|
|
|
|
use the original creation date of the old data to calculate the index age.
|
