IN-654 up elasticache clusters to be inline with sirius availability … #35
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
jamesrwarren
force-pushed
the
IN-654
branch
2 times, most recently
from
8e38a57 to
ea1f9ec
Compare
jackgoodby
approved these changes
Apr 7, 2021
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.
Purpose
It has been requested that all sirius related infra be truly multi az. Making elasticache multi AZ
Approach
These changes are very destructive in terms of elasticache cluster. However I have tested running load tests against the env whilst making the changes and it comes back fine so as long as sirius isn't down whilst we are replacing this then we should be ok.
Learning
NA
Checklist