[X] I had searched in the issues and found no similar issues.
What happened
I stopped the workflow manually while the workflow was running, and then the status of the workflow was always ready to stop. In the metadata information, state is 4 and end_time is null. Although the spark task of this workflow is stopped, the running time of this workflow continues to increase.
What you expected to happen
I think it is the SUB_PROCESS node that is used, because after I manually stopped the workflow without using the SUB_PROCESS node, the situation described above did not occur.
How to reproduce
If you want to reproduce this situation, you can create a workflow A related to the spark on yarn task, and then use the SUB_PROCESS node in the new workflow to reference workflow A. Manually stop the workflow during the running phase and observe the phenomenon.
Search before asking
What happened
I stopped the workflow manually while the workflow was running, and then the status of the workflow was always ready to stop. In the metadata information, state is 4 and end_time is null. Although the spark task of this workflow is stopped, the running time of this workflow continues to increase.
What you expected to happen
I think it is the SUB_PROCESS node that is used, because after I manually stopped the workflow without using the SUB_PROCESS node, the situation described above did not occur.
How to reproduce
If you want to reproduce this situation, you can create a workflow A related to the spark on yarn task, and then use the SUB_PROCESS node in the new workflow to reference workflow A. Manually stop the workflow during the running phase and observe the phenomenon.
Anything else
No response
Version
3.1.x
Are you willing to submit PR?
Code of Conduct