mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-30 11:58:36 +00:00
27f13267f0
This adds release note highlights for the data tiers formalization feature. Relates to #60848
62 lines
2.5 KiB
Plaintext
62 lines
2.5 KiB
Plaintext
[[release-highlights]]
|
|
== What's new in {minor-version}
|
|
|
|
coming[{minor-version}]
|
|
|
|
Here are the highlights of what's new and improved in {es} {minor-version}!
|
|
ifeval::["{release-state}"!="unreleased"]
|
|
For detailed information about this release, see the
|
|
<<release-notes-{elasticsearch_version}, Release notes >> and
|
|
<<breaking-changes-{minor-version}, Breaking changes>>.
|
|
endif::[]
|
|
|
|
// Add previous release to the list
|
|
Other versions:
|
|
{ref-bare}/7.9/release-highlights.html[7.9]
|
|
| {ref-bare}/7.8/release-highlights.html[7.8]
|
|
| {ref-bare}/7.7/release-highlights.html[7.7]
|
|
| {ref-bare}/7.6/release-highlights-7.6.0.html[7.6]
|
|
| {ref-bare}/7.5/release-highlights-7.5.0.html[7.5]
|
|
| {ref-bare}/7.4/release-highlights-7.4.0.html[7.4]
|
|
| {ref-bare}/7.3/release-highlights-7.3.0.html[7.3]
|
|
| {ref-bare}/7.2/release-highlights-7.2.0.html[7.2]
|
|
| {ref-bare}/7.1/release-highlights-7.1.0.html[7.1]
|
|
| {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
|
|
// should be featured in the Stack Installation and Upgrade Guide:
|
|
// tag::notable-highlights[]
|
|
// [discrete]
|
|
// === Heading
|
|
//
|
|
// Description.
|
|
// end::notable-highlights[]
|
|
|
|
// Omit the notable highlights tag for entries that only need to appear in the ES ref:
|
|
// [discrete]
|
|
// === Heading
|
|
//
|
|
// Description.
|