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

Cold tier time-range should not be specified (#65546) 

Whether the cold tier can handle years depends a lot on the use case and
for instance our BWC guarantees. This would need to be part of a
specific sizing exercise, so in the spirit of not over-promising, the
description of the cold tier has been changed to not mention years.
This commit is contained in:
Henning Andersen 2020-11-30 15:04:41 +01:00 committed by Henning Andersen
parent aa8ebeb918
commit 9564a8b1e0
1 changed files with 33 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/datatiers.asciidoc
View File

@ -73,8 +73,8 @@ For resiliency, indices in the warm tier should be configured to use one or more
[[cold-tier]]
=== Cold tier
Once data in the warm tier is no longer being updated, it can move to the cold tier.
The cold tier typically holds the data from recent months or years.
Once data is no longer being updated, it can move from the warm tier to the cold tier where it
stays for the rest of its life.
The cold tier is still a responsive query tier, but data in the cold tier is not normally updated.
As data transitions into the cold tier it can be compressed and shrunken.
For resiliency, indices in the cold tier can rely on