-
Notifications
You must be signed in to change notification settings - Fork 59
Adding flags for ignore-retry-cause and default-max-attempts #596
Conversation
Signed-off-by: Daniel Rammer <daniel@union.ai>
Signed-off-by: Daniel Rammer <daniel@union.ai>
Signed-off-by: Dennis Keck <26092524+fellhorn@users.noreply.github.com>
Signed-off-by: Daniel Rammer <daniel@union.ai>
Signed-off-by: Daniel Rammer <daniel@union.ai>
In the current implementation enabling |
Signed-off-by: Daniel Rammer <daniel@union.ai>
Signed-off-by: Daniel Rammer <daniel@union.ai>
Codecov Report
Additional details and impacted files |
* Cleanup retry behavior Signed-off-by: Dennis Keck <26092524+fellhorn@users.noreply.github.com> * Fix interruptible retry threshold for odl behavior Signed-off-by: Dennis Keck <26092524+fellhorn@users.noreply.github.com> * Add tests for BuildNodeExecutionContext Signed-off-by: Dennis Keck <26092524+fellhorn@users.noreply.github.com> * Fix IsElgibileForRetries Tests Signed-off-by: Dennis Keck <26092524+fellhorn@users.noreply.github.com> --------- Signed-off-by: Dennis Keck <26092524+fellhorn@users.noreply.github.com>
Signed-off-by: Daniel Rammer <daniel@union.ai>
Signed-off-by: Daniel Rammer <daniel@union.ai>
Signed-off-by: Daniel Rammer <daniel@union.ai>
Signed-off-by: Daniel Rammer <daniel@union.ai>
Signed-off-by: Daniel Rammer <daniel@union.ai>
// interruptible machine | ||
maxAttempts := uint32(config.GetConfig().NodeConfig.DefaultMaxAttempts) | ||
if n.GetRetryStrategy() != nil && n.GetRetryStrategy().MinAttempts != nil && *n.GetRetryStrategy().MinAttempts != 1 { | ||
maxAttempts = uint32(*n.GetRetryStrategy().MinAttempts) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we deprecate MinAttempts
and add MaxAttempts
😂
Hi, we are moving all Flyte development to a monorepo. In order to help the transition period, we're moving open PRs to monorepo automatically and your PR was moved to flyteorg/flyte#4153. Notice that if there are any conflicts in the resulting PR they most likely happen due to the change in the import path of the flyte components. |
TL;DR
Adding flags to simplify retry behavior.
ignore-retry-cause
means that system and user failures are treated the same anddefault-max-attempts
sets a default number of retries for tasks.Type
Are all requirements met?
Complete description
^^^
Tracking Issue
NA
Follow-up issue
NA