-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Memoization doesn't work in templates that are dag or use retries #10426
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
Despite argoproj#10769 and argoproj#10426 both having examples of memoization not working with the examples having no output, no-one has picked up on this. To address this improve the documentation for memoization and work-avoidance, linking the two ideas and pointing people who want to skip steps towards work-avoidance unless they are really doing what memoization was designed to do. Issue argoproj#10426 is problematic in that some steps get memoized when perhaps they should't, so this commit shouldn't close it. Fixes argoproj#10769 Signed-off-by: Alan Clucas <[email protected]>
Please note: I am not totally in favour of this change, it makes memoization work without outputs and I'm not conviced this is actually healthy, but it's what people seem to expect. See the linked issues in the fixes list below. This change will cause memoization to work for all step and dag tasks even without outputs. Note: They were working semi-erroneously for some dag tasks due to implicit outputs before this change. Fixes argoproj#11280 (raised to cover this desire) Fixes argoproj#10769 (already closed by documentation) Partially addresses argoproj#10426: Dags will memoize now, but retries still won't Signed-off-by: Alan Clucas <[email protected]>
Please note: I am not totally in favour of this change, it makes memoization work without outputs and I'm not conviced this is actually healthy, but it's what people seem to expect. See the linked issues in the fixes list below. This change will cause memoization to work for all step and dag tasks even without outputs. Note: They were working semi-erroneously for some dag tasks due to implicit outputs before this change. Fixes argoproj#11280 (raised to cover this desire) Fixes argoproj#10769 (already closed by documentation) Partially addresses argoproj#10426: Dags will memoize now, but retries still won't Signed-off-by: Alan Clucas <[email protected]>
This should be improved but not fixed in 3.5, via #11379. The dag case now memoizes, but the retries don't. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
: argoproj#12490 argoproj#10426 (argoproj#12491) Signed-off-by: Isitha Subasinghe <[email protected]>
Pre-requisites
:latest
What happened/what you expected to happen?
When I add memoization to a step with
retryStrategy
, the memoization doesn't work.Checked with
retryStrategy: Always
and the defaultOnFailure
value.Also, the memoization doesn't work for a step which is a
dag
containing other steps.From the logs of the controller I can conclude that the entry in ConfigMap is not created for some reason after the retry/dag steps finish.
Version
3.4.4
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: