From b100f0403857b5f0447e04b24756ced5ef0ff4d8 Mon Sep 17 00:00:00 2001 From: James Rodewig Date: Wed, 3 Apr 2019 13:49:20 -0400 Subject: [PATCH] [DOCS] Note index rollover is not automatically monitored (#40464) --- docs/reference/indices/rollover-index.asciidoc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/reference/indices/rollover-index.asciidoc b/docs/reference/indices/rollover-index.asciidoc index 941942a171e30..7f6c3d0452a2d 100644 --- a/docs/reference/indices/rollover-index.asciidoc +++ b/docs/reference/indices/rollover-index.asciidoc @@ -1,8 +1,14 @@ [[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. 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