Clarify high availability recommendations in Elasticsearch orchestration docs #8151
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
👋 howdy, team! Can we call out that our recommendation for updates applying to highly available clusters should be multiple nodes per data tier and not just multiple nodes. (Multiple nodes would potentially keep responsiveness as long as master-eligible, but this avoids `status:red` search/ingestion issues.)
stefnestor
added
>enhancement
stefnestor
commented
Oct 22, 2024
docs/orchestrating-elastic-stack-applications/elasticsearch/orchestration.asciidoc
Outdated
Show resolved
Hide resolved
…chestration.asciidoc Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
|
Thanks, @kilfoyle ! While I believe this is true (as it is true for other Elastic platforms like self-hosted and ESS/ECE), my team had some uncertainty to confirm this is also true for ECK. Could we flag this requiring Dev sign-off? (Alternative, ECK could temporarily remove |
Yup! If my memory serves, I don't think I can merge anything in this repo without the ECK team first giving it a thumbs up. :-) |
|
@elasticmachine run docs-build |
pebrc
reviewed
Oct 24, 2024
docs/orchestrating-elastic-stack-applications/elasticsearch/orchestration.asciidoc
Outdated
Show resolved
Hide resolved
thbkrkr
approved these changes
Oct 25, 2024
thbkrkr
changed the title
thbkrkr
pushed a commit
that referenced
this pull request
Oct 25, 2024
…ion docs (#8151) This updates the orchestration documentation to clarify high availability setup recommendations. --------- Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Co-authored-by: Peter Brachwitz <peter.brachwitz@elastic.co>
thbkrkr
added a commit
that referenced
this pull request
Oct 28, 2024
…ion docs (#8151) (#8154) This updates the orchestration documentation to clarify high availability setup recommendations. --------- Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Co-authored-by: Peter Brachwitz <peter.brachwitz@elastic.co> Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
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.
👋 howdy, team! Can we call out that our recommendation for updates applying to highly available clusters should be multiple nodes per data tier and not just multiple nodes. (Multiple nodes would potentially keep responsiveness as long as master-eligible, but this avoids
status:redsearch/ingestion issues.)