aws: support multiple subnets to handle capacity issues#92
Open
emilyalbini wants to merge 1 commit intomainfrom
Open
aws: support multiple subnets to handle capacity issues#92emilyalbini wants to merge 1 commit intomainfrom
emilyalbini wants to merge 1 commit intomainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We ran into a problem yesterday where the AZ we run jobs on ran out of an instance type, delaying jobs.
This adds support for specifying more than one subnet in the configuration file, and in case of capacity errors it falls back to the next subnet on the list. It maintains the current behavior of always spawning all jobs in the first subnet if there is enough capacity.