From e7ddc45ddb7ce30430819d0993cd0200cfd22c53 Mon Sep 17 00:00:00 2001 From: Aria Marble <111301581+ariamarble@users.noreply.github.com> Date: Fri, 10 Mar 2023 10:10:18 -0800 Subject: [PATCH] Updates read only and rollover sections for ISM (#3349) * Updates read only and rollover sections Signed-off-by: ariamarble * Apply suggestions from code review Co-authored-by: Melissa Vagi <105296784+vagimeli@users.noreply.github.com> * Update _im-plugin/ism/policies.md --------- Signed-off-by: ariamarble Co-authored-by: Melissa Vagi <105296784+vagimeli@users.noreply.github.com> --- _im-plugin/ism/policies.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/_im-plugin/ism/policies.md b/_im-plugin/ism/policies.md index baa4378f..02a14d8d 100644 --- a/_im-plugin/ism/policies.md +++ b/_im-plugin/ism/policies.md @@ -136,6 +136,8 @@ Sets a managed index to be read only. } ``` +Set the index setting `index.blocks.write` to `true` for a managed index. ***Note:** this block does not prevent the index from refreshing. + ### read_write Sets a managed index to be writeable. @@ -257,7 +259,9 @@ Deletes a managed index. Rolls an alias over to a new index when the managed index meets one of the rollover conditions. -**Important**: ISM checks the conditions for operations on **every execution of the policy** based on the **set interval**, _not_ continuously. The rollover will be performed if the value **has reached** or _exceeded_ the configured limit **when the check is performed**. For example with `min_size` configured to a value of 100GiB, ISM might check the index at 99 GiB and not perform the rollover. However, if the index has grown past the limit (e.g. 105GiB) by the next check, the operation is performed. +ISM checks the conditions for operations on **every execution of the policy** based on the **set interval**, _not_ continuously. The rollover will be performed if the value **has reached** or _has exceeded_ the configured limit **when the check is performed**. For example with `min_size` configured to a value of 100GiB, ISM might check the index at 99 GiB and not perform the rollover. However, if the index has grown past the limit (e.g., 105GiB) by the next check, the operation is performed. + +If you need to skip the rollover action, you can set the index setting `index.plugins.index_state_management.rollover_skip` to `true`. For example, if you receive the error message "Missing alias or not the write index...", you can set the `index.plugins.index_state_management.rollover_skip` parameter to `true` and retry to skip rollover action. The index format must match the pattern: `^.*-\d+$`. For example, `(logs-000001)`. Set `index.plugins.index_state_management.rollover_alias` as the alias to rollover.