Remove leftover secure instances in service maintenance #4420
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
Now and then there are leftover secure instances, probably when worker instances get terminated during builds, this is possible in ASGs. 2 hours as a cutoff should be enough, since the build times out after 60 minutes, and fetching the output archive after 30 minutes, so that leaves 30 minutes for booting and connection.
croissanne
changed the title
schuellerf
previously approved these changes
Oct 22, 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.
Now and then there are leftover secure instances, probably when worker instances get terminated during builds, this is possible in ASGs. 2 hours as a cutoff should be enough, since the build times out after 60 minutes, and fetching the output archive after 30 minutes, so that leaves 30 minutes for booting and connection.