ilm-settings.asciidoc 2.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566
  1. [role="xpack"]
  2. [[ilm-settings]]
  3. === {ilm-cap} settings in {es}
  4. [subs="attributes"]
  5. ++++
  6. <titleabbrev>{ilm-cap} settings</titleabbrev>
  7. ++++
  8. These are the settings available for configuring <<index-lifecycle-management, {ilm}>> ({ilm-init}).
  9. ==== Cluster level settings
  10. `xpack.ilm.enabled`::
  11. (boolean)
  12. deprecated:[7.8.0,Basic License features are always enabled] +
  13. This deprecated setting has no effect and will be removed in Elasticsearch 8.0.
  14. `indices.lifecycle.history_index_enabled`::
  15. (boolean)
  16. Whether ILM's history index is enabled. If enabled, ILM will record the
  17. history of actions taken as part of ILM policies to the `ilm-history-*`
  18. indices. Defaults to `true`.
  19. `indices.lifecycle.poll_interval`::
  20. (<<cluster-update-settings,Dynamic>>, <<time-units, time unit value>>)
  21. How often {ilm} checks for indices that meet policy criteria. Defaults to `10m`.
  22. ==== Index level settings
  23. These index-level {ilm-init} settings are typically configured through index
  24. templates. For more information, see <<ilm-gs-create-policy>>.
  25. `index.lifecycle.indexing_complete`::
  26. (<<indices-update-settings,Dynamic>>, boolean)
  27. Indicates whether or not the index has been rolled over.
  28. Automatically set to `true` when {ilm-init} completes the rollover action.
  29. You can explicitly set it to <<skipping-rollover, skip rollover>>.
  30. Defaults to `false`.
  31. `index.lifecycle.name`::
  32. (<<indices-update-settings, Dynamic>>, string)
  33. The name of the policy to use to manage the index.
  34. [[index-lifecycle-origination-date]]
  35. `index.lifecycle.origination_date`::
  36. (<<indices-update-settings,Dynamic>>, long)
  37. If specified, this is the timestamp used to calculate the index age for its phase transitions.
  38. Use this setting if you create a new index that contains old data and
  39. want to use the original creation date to calculate the index age.
  40. Specified as a Unix epoch value.
  41. `index.lifecycle.parse_origination_date`::
  42. (<<indices-update-settings,Dynamic>>, boolean)
  43. Set to `true` to parse the origination date from the index name.
  44. This origination date is used to calculate the index age for its phase transitions.
  45. The index name must match the pattern `^.*-{date_format}-\\d+`,
  46. where the `date_format` is `yyyy.MM.dd` and the trailing digits are optional.
  47. An index that was rolled over would normally match the full format,
  48. for example `logs-2016.10.31-000002`).
  49. If the index name doesn't match the pattern, index creation fails.
  50. `index.lifecycle.rollover_alias`::
  51. (<<indices-update-settings,Dynamic>>, string)
  52. The index alias to update when the index rolls over. Specify when using a
  53. policy that contains a rollover action. When the index rolls over, the alias is
  54. updated to reflect that the index is no longer the write index. For more
  55. information about rolling indices, see <<index-rollover, Rollover>>.