github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-24 23:27:25 -04:00
Code Issues Projects Releases Packages Wiki Activity

Set recovery rate for dedicated cold nodes (#68480)

Browse source 
This commit sets the recovery rate for dedicated cold nodes. The goal is
here is enhance performance of recovery in a dedicated cold tier, where
we expect such nodes to be predominantly using searchable snapshots to
back the indices located on them. This commit follows a simple approach
where we increase the recovery rate as a function of the node size, for
nodes that appear to be dedicated cold nodes.
This commit is contained in:
Jason Tedor 2021-02-04 10:36:07 -05:00 • committed by GitHub
parent fdb147ad6a
commit 6e94e67ae9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 65 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/reference/modules/indices/recovery.asciidoc
View file

@ -18,7 +18,21 @@ You can view a list of in-progress and completed recoveries using the
`indices.recovery.max_bytes_per_sec`::
(<<cluster-update-settings,Dynamic>>) Limits total inbound and outbound
recovery traffic for each node. Applies to both peer recoveries as well
as snapshot recoveries (i.e., restores from a snapshot). Defaults to `40mb`.
as snapshot recoveries (i.e., restores from a snapshot). Defaults to `40mb`
unless the node is a <<cold-tier, dedicated cold node>> in which case the
default relates to the total memory available to the node:
.Recovery Rate for Cold Nodes
[options="header"]
|======
|total memory | default value
|<= 4 GB | 40 MB/s
|> 4 GB and <= 8 GB | 60 MB/s
|> 8 GB and <= 16 GB | 90 MB/s
|> 16 GB and <= 32 GB | 125 MB/s
|> 32 GB | 250 MB/s
|======
+
This limit applies to each node separately. If multiple nodes in a cluster
perform recoveries at the same time, the cluster's total recovery traffic may