[DOCS] Add API example + diagrams to shard allocation awareness docs #108390
+38
−17
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
shainaraskas
added
>docs
|
Documentation preview: |
|
Pinging @elastic/es-docs (Team:Docs) |
shainaraskas
added
the
:Distributed/Allocation
|
Pinging @elastic/es-distributed (Team:Distributed) |
DaveCTurner
reviewed
May 7, 2024
| if you want Elasticsearch to distribute shards across different racks, you might | ||
| set an awareness attribute called `rack_id` in each node's `elasticsearch.yml` | ||
| config file. | ||
| . In each node's `elasticsearch.yml` config file, specify the location of each node |
There was a problem hiding this comment.
You can specify the location of each node with a custom node attribute by setting a value in elasticsearch.yml or using the -E command line argument. I agree that it'd be good to mention that the setting goes in elasticsearch.yml, but the first sentence in this paragraph should really apply to both methods.
There was a problem hiding this comment.
thanks @DaveCTurner! I've restructured this step to take your feedback into consideration:
chriscressman
approved these changes
May 8, 2024
DaveCTurner
approved these changes
May 8, 2024
markjhoy
pushed a commit
to markjhoy/elasticsearch
that referenced
this pull request
May 9, 2024
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.
Based on customer feedback, adds an example cluster update settings API call inline for the shard allocation awareness docs. To address concerns about how to use zones in clusters overall, I added a note to the Resilience in larger clusters guidance. could consider adding diagrams to that resilience doc down the line as a part of the suggested architectures work.
Also adds diagrams so the relationship between shards and nodes given a specific node attribute is clearer.
platform docs reviewers: I kinda made these diagrams up. what do you think?
Changed pages