Hotfix: set worker ASG onDemandPercentageAboveBaseCapacity to 10
#85
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
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.
What does this change?
Sets worker autoscaling group on-demand percentage to 10%
Why
On-demand percentage of the worker ASG is currently 0% so when there are no spot instances available in our AWS region, the ASG is unable to scale with the transcription job queue. This happened over the weekend resulting in a backlog of 14 jobs and a few failed transcriptions. We should keep on-demand percentage at > 0% until we find a way to use 100% spot instances, unless there are none available, in which case we fall back to on-demand instances.
How to test
Deployed to prod