github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-06-28 17:34:17 -04:00
Code Issues Projects Releases Packages Wiki Activity

Add warning about restart migration (#116769)

Browse source 
We have gotten more than one SDH due to customers not understanding
why restarts involving fully-mounted indices can pull a lot of data
from the snapshot tier, so it may help to be more explicit about
why this happens and how it can be avoided.
This commit is contained in:
Brendan Cully 2024-11-14 09:07:09 -08:00 • committed by GitHub
parent 1a9302c0e0
commit b77df851b1
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 10 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/reference/searchable-snapshots/index.asciidoc
View file

@ -176,10 +176,10 @@ nodes that have a shared cache.
====
Manually mounting snapshots captured by an Index Lifecycle Management ({ilm-init}) policy can
interfere with {ilm-init}'s automatic management. This may lead to issues such as data loss
or complications with snapshot handling.
or complications with snapshot handling.
For optimal results, allow {ilm-init} to manage
snapshots automatically.
snapshots automatically.
<<ilm-searchable-snapshot,Learn more about {ilm-init} snapshot management>>.
====
@ -293,6 +293,14 @@ repository. If you wish to search data across multiple regions, configure
multiple clusters and use <<modules-cross-cluster-search,{ccs}>> or
<<xpack-ccr,{ccr}>> instead of {search-snaps}.
It's worth noting that if a searchable snapshot index has no replicas, then when the node
hosting it is shut down, allocation will immediately try to relocate the index to a new node
in order to maximize availability. For fully mounted indices this will result in the new node
downloading the entire index snapshot from the cloud repository. Under a rolling cluster restart,
this may happen multiple times for each searchable snapshot index. Temporarily
disabling allocation during planned node restart will prevent this, as described in
the <<restart-cluster-rolling,cluster restart procedure>>.
[discrete]
[[back-up-restore-searchable-snapshots]]
=== Back up and restore {search-snaps}