github-actions[bot] commented on issue #14169:
URL: 
https://github.com/apache/dolphinscheduler/issues/14169#issuecomment-1556377989

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   The failure strategy of the parent process instance is end, and the 
parallelism strategy is selected. When there are many subprocess type nodes, 
some subprocess instances have run successfully, but the subprocess task 
instances in the parent process have not been updated to complete status. At 
this time, a subprocess type node fails, and the parent process will kill all 
surviving tasks. Instance, all surviving subprocess-associated subprocess 
instances will be forcibly updated to the ready stop state, resulting in task 
instances in the parent process not being able to be updated, so it always 
shows that the submission is successful, or the running state
   
   >The failure policy of the parent process instance is end, and the 
parallelism policy is selected. When there are many subprocess type nodes, some 
subprocess instances have run successfully, but the subprocess task instances 
in the parent process have not been updated to complete status .At this time, a 
subprocess type node fails, and the parent process will kill all surviving 
tasks. instance, all surviving subprocess-associated subprocess instances will 
be forcibly updated to the ready stop state, resulting in task instances in the 
parent process not being updated
   
   ### What you expected to happen
   
   be right
   
   ### How to reproduce
   
   be right
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.1.x
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


-- 
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]

Reply via email to