mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 15:47:23 -04:00
118521d022
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> |
||
|---|---|---|
| .. | ||
| analysis-icu | ||
| analysis-kuromoji | ||
| analysis-nori | ||
| analysis-phonetic | ||
| analysis-smartcn | ||
| analysis-stempel | ||
| analysis-ukrainian | ||
| discovery-azure-classic | ||
| discovery-ec2 | ||
| discovery-gce | ||
| examples | ||
| ingest-attachment | ||
| mapper-annotated-text | ||
| mapper-murmur3 | ||
| mapper-size | ||
| repository-azure | ||
| repository-gcs | ||
| repository-hdfs | ||
| repository-s3 | ||
| store-smb | ||
| transport-nio | ||
| build.gradle | ||