From 14952dd5d49033fa64df8a6931f6fd62e45256e9 Mon Sep 17 00:00:00 2001 From: Ievgen Degtiarenko Date: Mon, 11 Nov 2024 15:59:11 +0100 Subject: [PATCH] Clarify docs around disk capacity expectation. (#115745) Make it explicit that es expects disks to have the same capacity across all the nodes in the same data tier. (cherry picked from commit 3ebc1f48aaed8bfaecbb86881503373f9bda2491) --- docs/reference/datatiers.asciidoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/reference/datatiers.asciidoc b/docs/reference/datatiers.asciidoc index d7d52e8595042..066765368ec5e 100644 --- a/docs/reference/datatiers.asciidoc +++ b/docs/reference/datatiers.asciidoc @@ -37,9 +37,8 @@ TIP: The performance of an {es} node is often limited by the performance of the For example hardware profiles, refer to Elastic Cloud's {cloud}/ec-reference-hardware.html[instance configurations]. Review our recommendations for optimizing your storage for <> and <>. -IMPORTANT: {es} generally expects nodes within a data tier to share the same -hardware profile. Variations not following this recommendation should be -carefully architected to avoid <>. +IMPORTANT: {es} assumes nodes within a data tier share the same hardware profile (such as CPU, RAM, disk capacity). +Data tiers with unequally resourced nodes have a higher risk of <>. The way data tiers are used often depends on the data's category: