From 4ac01fe5b586af200df6d8e2719253b4fcc594b6 Mon Sep 17 00:00:00 2001 From: Adam Locke Date: Wed, 13 Oct 2021 09:40:50 -0400 Subject: [PATCH] [7.8] [DOCS] Fix default value for closed indices (#78924) (#79068) * [DOCS] Fix default value for closed indices Closes #78877 * Update description * Update note to remove outdated claims --- docs/reference/modules/indices/index_management.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/reference/modules/indices/index_management.asciidoc b/docs/reference/modules/indices/index_management.asciidoc index b9b4213e5a25f..ab51950dab1aa 100644 --- a/docs/reference/modules/indices/index_management.asciidoc +++ b/docs/reference/modules/indices/index_management.asciidoc @@ -18,9 +18,10 @@ When set to `true`, you must specify the index name to <> in {es}. You might enable this setting temporarily to change the analyzer configuration for an existing index. We strongly recommend leaving this set to `false` (the default) otherwise. +Enables <> in {es}. If `false`, you +cannot close open indices. Defaults to `true`. + -IMPORTANT: Closed indices are a data loss risk because they are not included when you make cluster configuration changes, such as scaling to a different capacity, failover, and many other operations. Additionally, closed indices can lead to inaccurate disk space counts. +NOTE: Closed indices still consume a significant amount of disk space. [[reindex-remote-whitelist]] // tag::reindex-remote-whitelist[]