From 290d52f47bd9edeecc47b53cc36d953eaab196e6 Mon Sep 17 00:00:00 2001 From: James Rodewig <40268737+jrodewig@users.noreply.github.com> Date: Thu, 16 Sep 2021 16:36:41 -0400 Subject: [PATCH] [DOCS] Add deprecation docs for `cluster.routing.allocation.disk.include_relocations` (#77726) We deprecated the `cluster.routing.allocation.disk.include_relocations` setting in 7.5 with PR #47443. However, we didn't add a related item to the 7.5 deprecation docs. This adds the missing item. Relates to #47717. --- docs/reference/migration/migrate_7_5.asciidoc | 24 ++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/docs/reference/migration/migrate_7_5.asciidoc b/docs/reference/migration/migrate_7_5.asciidoc index 7db1961f86d14..941e710b09c9c 100644 --- a/docs/reference/migration/migrate_7_5.asciidoc +++ b/docs/reference/migration/migrate_7_5.asciidoc @@ -9,12 +9,32 @@ your application to Elasticsearch 7.5. See also <> and <>. +* <> +* <> + //NOTE: The notable-breaking-changes tagged regions are re-used in the //Installation and Upgrade Guide //tag::notable-breaking-changes[] -//end::notable-breaking-changes[] +[discrete] +[[breaking_75_allocation_deprecations]] +=== Allocation deprecations + +[discrete] +[[deprecate-cluster-routing-allocation-disk-include-relocations-setting]] +==== The `cluster.routing.allocation.disk.include_relocations` setting is deprecated. + +The `cluster.routing.allocation.disk.include_relocations` cluster setting is now +deprecated. In future versions, {es} will account for the sizes of relocating +shards when making allocation decisions based on the disk usage of nodes in the +cluster. + +Currently, you can set `cluster.routing.allocation.disk.include_relocations` to +`false` to disable this accounting. This can result in poor allocation decisions +that might overshoot watermarks and require significant work to correct. + +To avoid deprecation warnings, discontinue use of the setting. [discrete] [[breaking_75_search_changes]] @@ -26,3 +46,5 @@ Previously, a wildcard query on the `_index` field matched directly against the fully-qualified index name. Now, in order to match against remote indices like `cluster:index`, the query must contain a colon, as in `cl*ster:inde*`. This behavior aligns with the way indices are matched in the search endpoint. + +//end::notable-breaking-changes[] \ No newline at end of file