DarkAssassinator opened a new issue, #12001:
URL: https://github.com/apache/dolphinscheduler/issues/12001

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   after #12000 , i restart the master service to re-build the worker group 
cache in master service, then re-run the process instance.
   the UI should the process is running:
   
![image](https://user-images.githubusercontent.com/20518339/190634906-123cb622-cc5d-47f9-8b2b-93d49e962d94.png)
   and the log show many `due to no suitable worker`
   
![image](https://user-images.githubusercontent.com/20518339/190635092-67670556-e21b-434a-9cae-c9c3e3b1cb34.png)
   Because these failed taskinstance still will put the `TaskPriorityQueue` and 
infinite loop.
   I think that we should check the worker group before put it to the 
`TaskPriorityQueue`, because cannot find this worker group, still cannot back 
to success (just add the worker group).
   Validate the task instance before add to dispatch or loop should be better. 
If task instance invaild, avoid the infinite loop check and log print. 
   
   ### Are you willing to submit a 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