mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-06 13:08:29 +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>
13 lines
352 B
Plaintext
13 lines
352 B
Plaintext
`max_restore_bytes_per_sec`::
|
|
|
|
Throttles per node restore rate. Defaults to unlimited.
|
|
Note that restores are also throttled through {ref}/recovery.html[recovery settings].
|
|
|
|
`max_snapshot_bytes_per_sec`::
|
|
|
|
Throttles per node snapshot rate. Defaults to `40mb` per second.
|
|
|
|
`readonly`::
|
|
|
|
Makes repository read-only. Defaults to `false`.
|