Mrhs121 commented on issue #18318: URL: https://github.com/apache/dolphinscheduler/issues/18318#issuecomment-4627644037
I was able to reproduce this issue locally with your workflow. However, the issue is intermittent. I ran the workflow three times consecutively. For the first two runs, task3(sh3) failed and the workflow instance correctly transitioned to the failed state. On the third run, task3 still failed, but the workflow instance stayed in the RUNNING state, even though there were no tasks being executed. Also, when I manually clicked Stop on this stuck workflow instance, its state only changed to READY_STOP and never transitioned to the final STOP state. > It was discovered that it was not a problem with the restart. A simple method for reproducing the issue was found. Create one workflow with 5 shell tasks (sh1, sh2, sh3, sh4, sh5). sh1 -> sh3 -> sh5 sh2 -> sh4 > > Sh5 depends on sh3 and sh4, while sh3 depends on sh1, and sh4 depends on sh2. > > The codes for each shell node are as follows: sh1: echo 1 sh2: echo 1 sh3: aecho 1 (failed) sh4: echo 1 sh5: echo 1 Reproduction can be achieved by manually triggering the workflow execution. [@SbloodyS](https://github.com/SbloodyS) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
