From 60f8a32dbaca0fda525f5a7243c906c6cce992a2 Mon Sep 17 00:00:00 2001 From: debadair Date: Wed, 13 May 2020 16:12:37 -0700 Subject: [PATCH] [DOCS] Add info about ILM and unallocated shards. (#56655) (#56724) * [DOCS] Add info about ILM and unallocated shards. * Incorporated review feedback. * Update docs/reference/ilm/actions/ilm-allocate.asciidoc Co-authored-by: James Rodewig * Apply suggestions from code review Co-authored-by: James Rodewig * Fix xref Co-authored-by: James Rodewig Co-authored-by: James Rodewig --- docs/reference/ilm/actions/ilm-allocate.asciidoc | 8 ++++---- docs/reference/ilm/ilm-index-lifecycle.asciidoc | 9 +++++++++ 2 files changed, 13 insertions(+), 4 deletions(-) diff --git a/docs/reference/ilm/actions/ilm-allocate.asciidoc b/docs/reference/ilm/actions/ilm-allocate.asciidoc index 69ca1fcce87..13d1745d3d5 100644 --- a/docs/reference/ilm/actions/ilm-allocate.asciidoc +++ b/docs/reference/ilm/actions/ilm-allocate.asciidoc @@ -7,16 +7,16 @@ Phases allowed: warm, cold. Updates the index settings to change which nodes are allowed to host the index shards and change the number of replicas. +The allocate action is not allowed in the hot phase. +The initial allocation for the index must be done manually or via +<>. + You can configure this action to modify both the allocation rules and number of replicas, only the allocation rules, or only the number of replicas. - For more information about how {es} uses replicas for scaling, see <>. See <> for more information about controlling where {es} allocates shards of a particular index. -NOTE: The allocate action is not allowed in the hot phase. -The initial allocation for the index must be done manually or via index templates. -{ilm-init} doesn't handle index allocation during the hot phase. [[ilm-allocate-options]] ==== Options diff --git a/docs/reference/ilm/ilm-index-lifecycle.asciidoc b/docs/reference/ilm/ilm-index-lifecycle.asciidoc index c03fbdb7bee..b249b4c8f5d 100644 --- a/docs/reference/ilm/ilm-index-lifecycle.asciidoc +++ b/docs/reference/ilm/ilm-index-lifecycle.asciidoc @@ -36,6 +36,15 @@ the index must be older than the minimum age of the next phase. The minimum age defaults to zero, which causes {ilm-init} to move indices to the next phase as soon as all actions in the current phase complete. +If an index has unallocated shards and the <> is yellow, +the index can still transition to the next phase according to its {ilm} policy. +However, because {es} can only perform certain clean up tasks on a green +cluster, there might be unexpected side effects. + +To avoid increased disk usage and reliability issues, +address any cluster health problems in a timely fashion. + + [discrete] [[ilm-phase-execution]] === Phase execution