mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-10 06:55:32 +00:00
15c85b29fd
Restoring from a snapshot (which is a particular form of recovery) does not currently take recovery throttling into account (i.e. the `indices.recovery.max_bytes_per_sec` setting). While restores are subject to their own throttling (repository setting `max_restore_bytes_per_sec`), this repository setting does not allow for values to be configured differently on a per-node basis. As restores are very similar in nature to peer recoveries (streaming bytes to the node), it makes sense to configure throttling in a single place. The `max_restore_bytes_per_sec` setting is also changed to default to unlimited now, whereas previously it was set to `40mb`, which is the current default of `indices.recovery.max_bytes_per_sec`). This means that no behavioral change will be observed by clusters where the recovery and restore settings were not adapted. Relates https://github.com/elastic/elasticsearch/issues/57023 Co-authored-by: James Rodewig <james.rodewig@elastic.co>
25 lines
1.0 KiB
Plaintext
25 lines
1.0 KiB
Plaintext
[[release-notes-7.9.0]]
|
|
== {es} version 7.9.0
|
|
|
|
Also see <<breaking-changes-7.9,Breaking changes in 7.9>>.
|
|
|
|
[[breaking-7.9.0]]
|
|
[float]
|
|
=== Breaking changes
|
|
|
|
Script Cache::
|
|
* Script cache size and rate limiting are per-context {es-pull}55753[#55753] (issue: {es-issue}50152[#50152])
|
|
|
|
Field capabilities API::
|
|
* Constant_keyword fields are now described by their family type `keyword` instead of `constant_keyword` {es-pull}58483[#58483] (issue: {es-issue}53175[#53175])
|
|
|
|
Snapshot restore throttling::
|
|
* Restoring from a snapshot (which is a particular form of recovery) is now
|
|
properly taking recovery throttling into account (i.e. the
|
|
`indices.recovery.max_bytes_per_sec` setting).
|
|
The `max_restore_bytes_per_sec` setting is also now defaulting to
|
|
unlimited, whereas previously it was set to `40mb`, which is the
|
|
default that's used for `indices.recovery.max_bytes_per_sec`. This means
|
|
that no behavioral change will be observed by clusters where the recovery
|
|
and restore settings had not been adapted from the defaults. {es-pull}58658[#58658]
|