2015-06-22 23:49:45 +02:00
|
|
|
[[recovery]]
|
|
|
|
|
=== Indices Recovery
|
|
|
|
|
|
2019-01-09 08:18:25 +00:00
|
|
|
<<cat-recovery,Peer recovery>> is the process used to build a new copy of a
|
|
|
|
|
shard on a node by copying data from the primary. {es} uses this peer recovery
|
|
|
|
|
process to rebuild shard copies that were lost if a node has failed, and uses
|
|
|
|
|
the same process when migrating a shard copy between nodes to rebalance the
|
|
|
|
|
cluster or to honor any changes to the <<modules-cluster,shard allocation
|
|
|
|
|
settings>>.
|
|
|
|
|
|
|
|
|
|
The following _expert_ setting can be set to manage the resources consumed by
|
|
|
|
|
peer recoveries:
|
2015-06-22 23:49:45 +02:00
|
|
|
|
|
|
|
|
`indices.recovery.max_bytes_per_sec`::
|
2019-01-09 08:18:25 +00:00
|
|
|
Limits the total inbound and outbound peer recovery traffic on each node.
|
|
|
|
|
Since this limit applies on each node, but there may be many nodes
|
|
|
|
|
performing peer recoveries concurrently, the total amount of peer recovery
|
|
|
|
|
traffic within a cluster may be much higher than this limit. If you set
|
|
|
|
|
this limit too high then there is a risk that ongoing peer recoveries will
|
|
|
|
|
consume an excess of bandwidth (or other resources) which could destabilize
|
|
|
|
|
the cluster. Defaults to `40mb`.
|
2015-06-22 23:49:45 +02:00
|
|
|
|
2017-01-31 18:05:42 +05:30
|
|
|
This setting can be dynamically updated on a live cluster with the
|
2019-01-09 08:18:25 +00:00
|
|
|
<<cluster-update-settings,cluster-update-settings>> API.
|
