Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support workflow and step level retry strategy #451

Closed
Ark-kun opened this issue Dec 4, 2018 · 6 comments
Closed

Support workflow and step level retry strategy #451

Ark-kun opened this issue Dec 4, 2018 · 6 comments

Comments

@Ark-kun
Copy link
Contributor

Ark-kun commented Dec 4, 2018

No description provided.

@Ark-kun Ark-kun changed the title Add ContainerOp.with_retryStrategy() Add ContainerOp.with_retry_strategy() Dec 4, 2018
@Ark-kun Ark-kun changed the title Add ContainerOp.with_retry_strategy() Add ContainerOp.with_retry_strategy(limit: int) Dec 4, 2018
@vicaire vicaire changed the title Add ContainerOp.with_retry_strategy(limit: int) Support workflow and step level retry strategy Mar 26, 2019
@gaoning777
Copy link
Contributor

we already supported step level retry:

def set_retry(self, num_retries: int):

@gaoning777
Copy link
Contributor

Argo does not have workflow level retry.
DSL has a sample to illustrate how to apply a transformer to all ops in a pipeline: #1440

@ketanio
Copy link

ketanio commented Jun 10, 2019

@gaoning777 Can we retry from the UI for a specific step?

@gaoning777
Copy link
Contributor

Unfortunately not. Currently, the retry can be configured in the DSL and the backend automatically retries the steps if they fail. If your user scenario is to be able to rerun a specific step, we are working on the KFP caching such that a pipeline can be rerun without rerunning all steps.

@kevinpauli
Copy link

we are working on the KFP caching such that a pipeline can be rerun without rerunning all steps.

@gaoning777 can you please provide a link to the GH issue that is tracking this effort?

@amclay
Copy link

amclay commented Sep 3, 2019

@gaoning777 I would also be interested in tracking this ticket if it exists. (for retrying individual steps)

Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
* Support Python functions in workflows

* Include job types

* Skip test

* Incorporate feedback

* Use single Workflow class

* Fix pylint instance attribs
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants