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

Add release note highlights for data tiers (#63427) 

This adds release note highlights for the data tiers formalization feature.

Relates to #60848
This commit is contained in:
Lee Hinman 2020-10-08 14:39:09 -06:00 committed by GitHub
parent ae2fc4118d
commit 27f13267f0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/reference/release-notes/highlights.asciidoc
View File

@ -23,7 +23,27 @@ Other versions:
| {ref-bare}/7.1/release-highlights-7.1.0.html[7.1] | {ref-bare}/7.1/release-highlights-7.1.0.html[7.1]
| {ref-bare}/7.0/release-highlights-7.0.0.html[7.0] | {ref-bare}/7.0/release-highlights-7.0.0.html[7.0]
// tag::notable-highlights[]
[discrete]
[[data-tier-formalization]]
=== Data Tier Formalization
7.10 introduces the concept of formalized data tiers within Elasticsearch. <<data-tiers,Data tiers>>
are a simple, integrated approach that gives users control over optimizing for cost,
performance, and breadth/depth of data. Prior to this formalization, many users configured their own
tier topology using custom node attributes as well as using {ilm-init} to manage the lifecycle and
location of data within a cluster.
With this formalization, data tiers (content, hot, warm, and cold) can be explicitly configured
using <<node-roles,node roles>>, and indices can be configured to be allocated within a specific
tier using <<data-tier-shard-filtering,index-level data tier allocation filtering>>. {ilm-init} will
make use of these tiers to <<ilm-migrate,automatically migrate>> data between nodes as an index goes
through the phases of its lifecycle.
Newly created indices abstracted by a <<data-streams,data stream>> will be allocated to
the `data_hot` tier automatically, while standalone indices will be allocated to
the `data_content` tier automatically. Nodes with the pre-existing `data` role are
considered to be part of all tiers.
// end::notable-highlights[]
// Use the notable-highlights tag to mark entries that // Use the notable-highlights tag to mark entries that
// should be featured in the Stack Installation and Upgrade Guide: // should be featured in the Stack Installation and Upgrade Guide: