Open washcycle opened 1 year ago
@washcycle Can you provide more details about the scenario? GUI retry will restart the workflow from the fail step or task. Parallelism will control the # of parallel tasks during workflow execution.
What happens is that parallelism of the task seems to be ignored when using the GUI retry. If it had five failed tasks instead of retrying two tasks at a time it will retry all five at the same time.
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.
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.
Pre-requisites
:latest
What happened/what you expected to happen?
When a dag with parallelism fails and the user retires in the web GUI, the parallelism is no longer respected.
I expect retries to respect the level of parallelism for dags.
An non-ideal workaround is to specify parallelism at the workflow spec level as well.
Version
3.4.3
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