From 680999f246e0b1a31e0c63bac7e789800c2fd2f6 Mon Sep 17 00:00:00 2001 From: James Rodewig Date: Fri, 1 Nov 2019 11:54:13 -0400 Subject: [PATCH] [DOCS] List `indices.lifecycle.poll_interval` as cluster-level (#48813) Lists `indices.lifecycle.poll_interval` with other cluster-level ILM settings. Previously, it was included under index-level settings. --- docs/reference/settings/ilm-settings.asciidoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/settings/ilm-settings.asciidoc b/docs/reference/settings/ilm-settings.asciidoc index 97ae65d1815..8781581a6e5 100644 --- a/docs/reference/settings/ilm-settings.asciidoc +++ b/docs/reference/settings/ilm-settings.asciidoc @@ -10,6 +10,10 @@ These are the settings available for configuring Index Lifecycle Management Whether ILM is enabled or disabled, setting this to `false` disables any ILM REST API endpoints and functionality. Defaults to `true`. +`indices.lifecycle.poll_interval`:: +(<>) How often {ilm} checks for indices that meet policy +criteria. Defaults to `10m`. + ==== Index level settings These index-level {ilm-init} settings are typically configured through index templates. For more information, see <>. @@ -23,10 +27,6 @@ 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 <>. -`indices.lifecycle.poll_interval`:: -(<>) How often {ilm} checks for indices that meet policy -criteria. Defaults to `10m`. - `index.lifecycle.parse_origination_date`:: When configured to `true` the origination date will be parsed from the index name. The index format must match the pattern `^.*-{date_format}-\\d+`, where