Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.12] [DOCS] Add deprecation docs for cluster.routing.allocation.disk.include_relocations (#77726) #77941

Merged
merged 1 commit into from
Sep 16, 2021
Merged

[7.12] [DOCS] Add deprecation docs for cluster.routing.allocation.disk.include_relocations (#77726) #77941

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 23 additions & 1 deletion docs/reference/migration/migrate_7_5.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,32 @@ your application to Elasticsearch 7.5.

See also <<release-highlights>> and <<es-release-notes>>.

* <<breaking_75_allocation_deprecations>>
* <<breaking_75_search_changes>>

//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]]
Expand All @@ -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[]