|
@@ -53,12 +53,24 @@ In the cold phase, an index is no longer updated and seldom queried.
|
|
|
The information still needs to be searchable, but it’s okay if those queries are slower.
|
|
|
// end::cold-phase-def[]
|
|
|
|
|
|
+[[glossary-cold-tier]] cold tier::
|
|
|
+// tag::cold-tier-def[]
|
|
|
+A <<glossary-data-tier, data tier>> that contains nodes that hold time series data
|
|
|
+that is accessed occasionally and not normally updated.
|
|
|
+// end::cold-tier-def[]
|
|
|
+
|
|
|
[[glossary-component-template]] component template ::
|
|
|
// tag::component-template-def[]
|
|
|
A building block for constructing <<indices-templates,index templates>> that specifies index
|
|
|
<<mapping,mappings>>, <<index-modules-settings,settings>>, and <<indices-aliases,aliases>>.
|
|
|
// end::component-template-def[]
|
|
|
|
|
|
+[[glossary-content-tier]] content tier::
|
|
|
+// tag::content-tier-def[]
|
|
|
+A <<glossary-data-tier, data tier>> that contains nodes that handle the indexing and query load for
|
|
|
+content such as a product catalog.
|
|
|
+// end::content-tier-def[]
|
|
|
+
|
|
|
[[glossary-ccr]] {ccr} (CCR)::
|
|
|
// tag::ccr-def[]
|
|
|
A feature that enables you to replicate indices in remote clusters to your
|
|
@@ -86,6 +98,13 @@ See {ref}/data-streams.html[Data streams].
|
|
|
// end::data-stream-def[]
|
|
|
--
|
|
|
|
|
|
+[[glossary-data-tier]] data tier::
|
|
|
+// tag::data-tier-def[]
|
|
|
+A collection of nodes with the same data role that typically share the same hardware profile.
|
|
|
+See <<glossary-content-tier, content tier>>, <<glossary-hot-tier, hot tier>>, <<glossary-warm-tier, warm tier>>,
|
|
|
+<<glossary-cold-tier, cold tier>>.
|
|
|
+// end::data-tier-def[]
|
|
|
+
|
|
|
[[glossary-delete-phase]] delete phase ::
|
|
|
// tag::delete-phase-def[]
|
|
|
The last possible phase in the <<glossary-index-lifecycle,index lifecycle>>.
|
|
@@ -194,6 +213,13 @@ The first possible phase in the <<glossary-index-lifecycle,index lifecycle>>.
|
|
|
In the hot phase, an index is actively updated and queried.
|
|
|
// end::hot-phase-def[]
|
|
|
|
|
|
+[[glossary-hot-tier]] hot tier::
|
|
|
+// tag::hot-tier-def[]
|
|
|
+A <<glossary-data-tier, data tier>> that contains nodes that handle the indexing load
|
|
|
+for time series data such as logs or metrics and hold your most recent,
|
|
|
+most-frequently-accessed data.
|
|
|
+// end::hot-tier-def[]
|
|
|
+
|
|
|
[[glossary-id]] id ::
|
|
|
// tag::id-def[]
|
|
|
The ID of a <<glossary-document,document>> identifies a document. The
|
|
@@ -577,3 +603,9 @@ See {ref}/removal-of-types.html[Removal of mapping types].
|
|
|
The second possible phase in the <<glossary-index-lifecycle,index lifecycle>>.
|
|
|
In the warm phase, an index is generally optimized for search and no longer updated.
|
|
|
// end::warm-phase-def[]
|
|
|
+
|
|
|
+[[glossary-warm-tier]] warm tier::
|
|
|
+// tag::warm-tier-def[]
|
|
|
+A <<glossary-data-tier, data tier>> that contains nodes that hold time series data
|
|
|
+that is accessed less frequently and rarely needs to be updated.
|
|
|
+// end::warm-tier-def[]
|