You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
I created a dag where each task has an exit handler. In the example below, step-3 depends on step-2. After the fix of #3395 all exitHandlers are now being called as expected (thanks a lot to the team for this VERY quick fix). However if the exitHandler is defined as a DAG with multiple tasks only the first task seems to be run.
Anything else we need to know?:
However the exitHandler of the non-leaf task never registers as finished and thus keeps the workflow in status running indefinitely.
I saw similar behavior in 2.8.x where task-level non-leaf-task exitHandlers (defined as DAG) were started but then got stuck after 1 or 2 tasks.
arbielsk
changed the title
If non-leaf task onExit handler is defined as DAG only the first task is run
If non-leaf-task onExit-handler is defined as DAG only the first task is run
Jul 9, 2020
@simster7 Thank you very much for fixing these so quickly! I'd love to buy you a coffee if you allow me. If that's possible I'd appreciate some details via pm :)
Thanks again!
@simster7 Thank you very much for fixing these so quickly! I'd love to buy you a coffee if you allow me. If that's possible I'd appreciate some details via pm :)
Thanks again!
Thanks! No worries at all, positive feedback like this is as encouraging as coffee :)
Checklist:
What happened:
I created a dag where each task has an exit handler. In the example below, step-3 depends on step-2. After the fix of #3395 all exitHandlers are now being called as expected (thanks a lot to the team for this VERY quick fix). However if the exitHandler is defined as a DAG with multiple tasks only the first task seems to be run.
Hypothesis: There might be a connected to #3431
What you expected to happen:
I expected all of the exitHandler's tasks to be run like any other DAG.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
However the exitHandler of the non-leaf task never registers as finished and thus keeps the workflow in status running indefinitely.
I saw similar behavior in 2.8.x where task-level non-leaf-task exitHandlers (defined as DAG) were started but then got stuck after 1 or 2 tasks.
Environment:
Other debugging information (if applicable):
(logs of pod that executed step-2.onExit.exit-1)
Logs
see above
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: