honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify searchable snapshot cost trade-offs (#65384) 

Clarify that searchable snapshots only result in cost savings for less
frequently accessed data and that the savings do not apply to the entire
cluster.
This commit is contained in:
Henning Andersen 2020-11-26 13:40:08 +01:00 committed by Henning Andersen
parent b4b4483e24
commit 9f35b3d402
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/reference/searchable-snapshots/index.asciidoc
View File

@ -12,11 +12,12 @@ searching any other index, and minimizes the need to access the snapshot
repository. Should a node fail, shards of a {search-snap} index are
automatically recovered from the snapshot repository.
This can result in significant cost savings. With {search-snaps}, you may be
able to halve your cluster size without increasing the risk of data loss or
reducing the amount of data you can search. Because {search-snaps} rely on the
same snapshot mechanism you use for backups, they have a minimal impact on your
snapshot repository storage costs.
This can result in significant cost savings for less frequently searched data.
With {search-snaps}, you no longer need an extra index shard copy to avoid data
loss, potentially halving the node local storage capacity necessary for
searching that data. Because {search-snaps} rely on the same snapshot mechanism
you use for backups, they have a minimal impact on your snapshot repository
storage costs.
[discrete]
[[using-searchable-snapshots]]