[Issue #7398] Scale OpenSearch out #7438
Open
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
mdragon
requested review from
chouinar,
joshtonava,
prasnava and
sean-navapbc
as code owners
mdragon
changed the title
mdragon
changed the title
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.
Summary
Work for #7398
Changes proposed
This is one of two scaling approaches we're preparing for scaling Search traffic.
This approach will scale our search nodes out by increasing the nodes from 3 to 6. This is the smallest increment we can make as we must adjust in multiples of our availability zone count which is 3.
We are reviewing the change, so we are ready, but not planning to apply/deploy the change yet.