Scale up old dhstore in prep for making it primary #2607
Merged
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
The current primary dhstore, where new data is written to, is nearly out of space. The oldest dhstore is only 61% full, so prepare it to become the priimary.
masih
requested changes
Apr 25, 2024
There was a problem hiding this comment.
The instance type needs to be updated for the resource increase to be schdulable. Otherwise, the pod cannot run since node selection cannot be met. Take a look at the deployment which has the resources reduced and use the same instance type for the other one.
Otherwise, LGTM. Left some questions/suggestions.
deploy/manifests/prod/us-east-2/tenant/storetheindex/dhstore-seka/deployment.yaml
Show resolved
Hide resolved
deploy/manifests/prod/us-east-2/tenant/storetheindex/dhstore/pvc-gp3.yaml
Show resolved
Hide resolved
masih
approved these changes
Apr 25, 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.
The current primary dhstore, where new data is written to, is nearly out of space. The oldest dhstore is only 61% full, so prepare it to become the primary.
Storage IOPS and throughput will be scaled up administratively with AWS volume management.
This also scales down dhstore-seka. dhstore-tetra will be scaled down after prod is using the new (refurbished) dhstore.