Skip to content

Clarify docs around disk capacity expectation. #115745

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Nov 11, 2024
Merged

Clarify docs around disk capacity expectation. #115745

Changes from 2 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
bd3e91d
Clarify docs around disk capacity expectation.
idegtiarenko Oct 28, 2024
345f192
reword message
idegtiarenko Oct 28, 2024
3a7d107
Reword
idegtiarenko Nov 6, 2024
b275292
Merge branch 'main' into doc_clarify_tier_node_disk
idegtiarenko Nov 6, 2024
df2d5c8
Update docs/reference/datatiers.asciidoc
idegtiarenko Nov 7, 2024
dfdb809
Update docs/reference/datatiers.asciidoc
idegtiarenko Nov 7, 2024
f708f71
Update datatiers.asciidoc
idegtiarenko Nov 11, 2024
25c1206
Merge branch 'main' into doc_clarify_tier_node_disk
idegtiarenko Nov 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/reference/datatiers.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,9 @@ 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 <<indexing-use-faster-hardware,indexing>> and <<search-use-faster-hardware,search>>.

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 <<hotspotting,hot spotting>>.
IMPORTANT: {es} generally expects nodes within a data tier to share the same hardware profile (such as CPU, RAM, disk capacity)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
IMPORTANT: {es} generally expects nodes within a data tier to share the same hardware profile (such as CPU, RAM, disk capacity)
IMPORTANT: By default, {es} assumes nodes within a data tier share the same hardware profile (such as CPU, RAM, disk capacity)

Should we potentially take out "generally" and/or add "by default" in order to firm this as baseline expectation? Or go as far to say ES "assumes" this is true so if you want to do different you need to "carefully architect" (I like that phrasing)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd just say "Elasticsearch expects"

as it spreads the load equally across all nodes within the data tier.
Variations not following this recommendation should be carefully architected to avoid <<hotspotting,hot spotting>>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This construction is a little confusing. What steps could someone take to "carefully architect" a node to avoid hot spotting? if we can't provide recommendations, I'd change this to "Data tiers with unequally resourced nodes are at risk of hot spotting."


The way data tiers are used often depends on the data's category:

Expand Down