From dd69ae95d750cc59b8a03add539abcd3f258aa6f Mon Sep 17 00:00:00 2001 From: David Turner Date: Wed, 24 Mar 2021 09:22:44 +0000 Subject: [PATCH] Note recovery settings affect searchable snapshots (#70771) Adds a short note that `max_restore_bytes_per_sec` and `indices.recovery.max_bytes_per_sec` also affect the recovery of a searchable snapshot index. --- docs/reference/modules/indices/recovery.asciidoc | 1 + docs/reference/searchable-snapshots/index.asciidoc | 7 +++++++ 2 files changed, 8 insertions(+) diff --git a/docs/reference/modules/indices/recovery.asciidoc b/docs/reference/modules/indices/recovery.asciidoc index 9660f1f37e679..2fff28302e2bd 100644 --- a/docs/reference/modules/indices/recovery.asciidoc +++ b/docs/reference/modules/indices/recovery.asciidoc @@ -13,6 +13,7 @@ You can view a list of in-progress and completed recoveries using the <>. [discrete] +[[recovery-settings]] ==== Recovery settings `indices.recovery.max_bytes_per_sec`:: diff --git a/docs/reference/searchable-snapshots/index.asciidoc b/docs/reference/searchable-snapshots/index.asciidoc index b9385ff57fc1b..ab9f5d36b5cfc 100644 --- a/docs/reference/searchable-snapshots/index.asciidoc +++ b/docs/reference/searchable-snapshots/index.asciidoc @@ -48,6 +48,13 @@ same mechanisms as for regular indices. For example, you could use <> to restrict {search-snap} shards to a subset of your nodes. +The speed of recovery of a {search-snap} index is limited by the repository +setting `max_restore_bytes_per_sec` and the node setting +`indices.recovery.max_bytes_per_sec` just like a normal restore operation. By +default `max_restore_bytes_per_sec` is unlimited, but the default for +`indices.recovery.max_bytes_per_sec` depends on the configuration of the node. +See <>. + We recommend that you <> indices to a single segment per shard before taking a snapshot that will be mounted as a {search-snap} index. Each read from a snapshot repository takes time and costs