Clarify docs around disk capacity expectation. #115745
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make it explicit that es expects disks to have the same capacity across all the nodes in the same data tier.
idegtiarenko
added
>docs
|
Documentation preview: |
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-distributed (Team:Distributed) |
stefnestor
reviewed
Oct 30, 2024
docs/reference/datatiers.asciidoc
Outdated
| 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) |
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
I'd just say "Elasticsearch expects"
shainaraskas
reviewed
Nov 5, 2024
docs/reference/datatiers.asciidoc
Outdated
| 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) | ||
| 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>>. |
There was a problem hiding this comment.
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."
elasticsearchmachine
removed
the
Team:Distributed (Obsolete)
shainaraskas
approved these changes
Nov 6, 2024
Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: Henning Andersen <[email protected]>
|
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
elasticsearchmachine
added
the
Team:Distributed Coordination
jozala
pushed a commit
that referenced
this pull request
Nov 13, 2024
Make it explicit that es expects disks to have the same capacity across all the nodes in the same data tier.
afoucret
pushed a commit
to afoucret/elasticsearch
that referenced
this pull request
Nov 14, 2024
Make it explicit that es expects disks to have the same capacity across all the nodes in the same data tier.
alexey-ivanov-es
pushed a commit
to alexey-ivanov-es/elasticsearch
that referenced
this pull request
Nov 28, 2024
Make it explicit that es expects disks to have the same capacity across all the nodes in the same data tier.
This was referenced Jan 21, 2025
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
ywangd
pushed a commit
to ywangd/elasticsearch
that referenced
this pull request
Jan 21, 2025
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 3ebc1f4)
ywangd
pushed a commit
to ywangd/elasticsearch
that referenced
this pull request
Jan 21, 2025
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 3ebc1f4)
ywangd
pushed a commit
to ywangd/elasticsearch
that referenced
this pull request
Jan 21, 2025
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 3ebc1f4)
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 21, 2025
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 3ebc1f4) Co-authored-by: Ievgen Degtiarenko <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 21, 2025
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 3ebc1f4) Co-authored-by: Ievgen Degtiarenko <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 21, 2025
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 3ebc1f4) Co-authored-by: Ievgen Degtiarenko <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make it explicit that es expects disks to have the same capacity across all the nodes in the same data tier.