Implement new improved retry logic#1282
Merged
Merged
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
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.
Closes #1200
This PR introduces
retryproperty to profiles and run configurations as a replacement forretry_policy. It allows specifying different events that should be handled with retry. For example, users may retry provisioning the compute if there is no capacity:Supported events are
no-capacity,interruption, anderror.The duration is now calculated as a run age for
no-capacityand as a time passed since the lastinterruptionanderrorforinterruptionanderrorevents. For example, when specifyingdstack will try provisioning a new instance for 5m since the interruption. If there is no capacity for >5m, the run fails.
TODO: