reele commented on issue #16767:
URL: 
https://github.com/apache/dolphinscheduler/issues/16767#issuecomment-2471048938

   @SbloodyS 
   I'm sorry if my previous description was unclear. This issue is mainly about 
fault tolerance in sub-workflow. 
   
   Below is a detailed reproduce.
   
   there is the schedule tree:
   ```
   MAIN_WORKFLOW
       SUB_WORKFLOW
           STEP1->STEP2->STEP3->STEP4->STEP5
   ```
   
![1](https://github.com/user-attachments/assets/ca086bcc-9835-42d5-8c4f-3581fa14360b)
   
![2](https://github.com/user-attachments/assets/26d99e55-d693-4c35-9e63-eae60758de5a)
   
   
   1. execute MAIN_WORKFLOW
   2. stop and start master-server 3 times :
   
   
![3](https://github.com/user-attachments/assets/664f0f70-8fdd-4aca-ae07-98f34e95551a)
   
   then the SUB_WORKFLOW executed 3 times, and are all running and be 
controlled in master:
   
   
![4](https://github.com/user-attachments/assets/0a05b900-94d8-4b34-baeb-8aec46c86f92)
   
   finally, they are all finished:
   
   
![5](https://github.com/user-attachments/assets/88c5e44d-53e5-4539-b08e-7a8228d74fc2)
   
   
   i tried to created a branch to fix it :
   
https://github.com/reele/dolphinscheduler/compare/dev-usable-fix-all...reele:dolphinscheduler:fix-takeover-wf?expand=1
   
   and that works well.
   


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