From 3660282968fa09de052f1d2014b219cba7a8be44 Mon Sep 17 00:00:00 2001 From: James Rodewig Date: Tue, 26 Mar 2019 09:25:59 -0400 Subject: [PATCH 1/2] Clarify that index rollover is not automatic --- docs/reference/indices/rollover-index.asciidoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/reference/indices/rollover-index.asciidoc b/docs/reference/indices/rollover-index.asciidoc index 941942a171e30..f22d1541a6014 100644 --- a/docs/reference/indices/rollover-index.asciidoc +++ b/docs/reference/indices/rollover-index.asciidoc @@ -1,8 +1,12 @@ [[indices-rollover-index]] == Rollover Index -The rollover index API rolls an alias over to a new index when the existing -index is considered to be too large or too old. +The rollover index API rolls an <> to a new index when +the existing index meets a condition you provide. You can use this API to retire +an index that becomes too large or too old. + +NOTE: To roll over an index, a condition must be met *when you call the API*. +{es} does not monitor the index after you receive an API response. The API accepts a single alias name and a list of `conditions`. The alias must point to a write index for a Rollover request to be valid. There are two ways this can be achieved, and depending on the configuration, the From c4e147c40da87c0db0f31af956dcf2c6878a77b1 Mon Sep 17 00:00:00 2001 From: James Rodewig Date: Wed, 27 Mar 2019 08:54:10 -0400 Subject: [PATCH 2/2] Direct users to ILM policies for automatic rollover --- docs/reference/indices/rollover-index.asciidoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/reference/indices/rollover-index.asciidoc b/docs/reference/indices/rollover-index.asciidoc index f22d1541a6014..7f6c3d0452a2d 100644 --- a/docs/reference/indices/rollover-index.asciidoc +++ b/docs/reference/indices/rollover-index.asciidoc @@ -6,7 +6,9 @@ the existing index meets a condition you provide. You can use this API to retire an index that becomes too large or too old. NOTE: To roll over an index, a condition must be met *when you call the API*. -{es} does not monitor the index after you receive an API response. +{es} does not monitor the index after you receive an API response. To +automatically roll over indices when a condition is met, you can use {es}'s +<>. The API accepts a single alias name and a list of `conditions`. The alias must point to a write index for a Rollover request to be valid. There are two ways this can be achieved, and depending on the configuration, the