Added additional entries for troubleshooting unhealthy cluster #119914
+45
−22
Conversation
This file contains 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
Reordered "Re-enable shard allocation" because not as common as other causes Added additional causes of yellow statuses Changed watermark commadn to include high and low watermark so users can make their cluster operate once again.
|
Documentation preview: |
elasticsearchmachine
added
v8.17.2
external-contributor
|
cc @georgewallace (can't personally add reviewers at the moment) |
georgewallace
added
>docs
|
Pinging @elastic/es-docs (Team:Docs) |
elasticsearchmachine
removed
the
needs:triage
leemthompo
added
the
auto-backport
leemthompo
reviewed
Jan 10, 2025
docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc
Outdated
Show resolved
Hide resolved
Comment on lines
+91
to
+95
| * If you manually restart a node, then it will temporarily cause an unhealthy cluster until the node has recovered. | ||
|
|
||
| * If you have a node that is overloaded or has stopped operating for any reason, then it will temporarily cause an unhealthy cluster. Nodes may disconnect because of prolonged garbage collection (GC) pauses, which can result from "out of memory" errors or high memory usage due to intensive search operations. See <<fix-cluster-status-jvm,Reduce JVM memory pressure>> for more JVM related issues. | ||
|
|
||
| * If nodes cannot reliably communicate due to networking issues, they may lose contact with one another. This can cause shards to become out of sync. You can often identify this issue by checking the logs for repeated messages about nodes leaving and rejoining the cluster. |
There was a problem hiding this comment.
Suggested change
| * If you manually restart a node, then it will temporarily cause an unhealthy cluster until the node has recovered. | |
| * If you have a node that is overloaded or has stopped operating for any reason, then it will temporarily cause an unhealthy cluster. Nodes may disconnect because of prolonged garbage collection (GC) pauses, which can result from "out of memory" errors or high memory usage due to intensive search operations. See <<fix-cluster-status-jvm,Reduce JVM memory pressure>> for more JVM related issues. | |
| * If nodes cannot reliably communicate due to networking issues, they may lose contact with one another. This can cause shards to become out of sync. You can often identify this issue by checking the logs for repeated messages about nodes leaving and rejoining the cluster. | |
| * A manual node restart will cause a temporary unhealthy cluster state until the node recovers. | |
| * Node overload or failure causes a temporary unhealthy cluster state. Prolonged garbage collection (GC) pauses, caused by out-of-memory errors or high memory usage during intensive searches, can trigger this state. See <<fix-cluster-status-jvm,Reduce JVM memory pressure>> for more JVM-related issues. | |
| * Network issues can prevent reliable node communication, causing shards to become out of sync. Check the logs for repeated messages about nodes leaving and rejoining the cluster. |
copyedit for concision
There was a problem hiding this comment.
I like these edits but "Node overload or failure causes a temporary unhealthy cluster state" isn't clear to me.
How do you feel about
"When a node becomes overloaded or fails, it can temporarily disrupt the cluster’s health, leading to an unhealthy state."
docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc
Outdated
Show resolved
Hide resolved
|
run docs-build |
docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc
Outdated
Show resolved
Hide resolved
…fixes. Co-authored-by: Liam Thompson <[email protected]>
Co-authored-by: Liam Thompson <[email protected]>
Co-authored-by: Liam Thompson <[email protected]>
…r-status.asciidoc Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: Liam Thompson <[email protected]>
…r-status.asciidoc Co-authored-by: Liam Thompson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reordered "Re-enable shard allocation" because not as common as other causes
Added additional causes of yellow statuses
Changed watermark command to include high and low watermark so users can make their cluster operate once again.