q4q5q6qw opened a new issue, #15761: URL: https://github.com/apache/dolphinscheduler/issues/15761
### 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 First, create a shell workflow that contains only one shell script task. After the workflow runs properly, the monitoring information on the portal shows that the worker node breaks down. At this time, tasks in the workflow instance list are being delivered properly, but a new task instance is delivered for the tasks in the same workflow every second. After the worker node is restarted, the repeated tasks are executed concurrently. As a result, the CPU of the worker node explodes. ### What you expected to happen Tasks Are Not Repeatedly Delivered After the Worker Breaks Down ### How to reproduce Prepare a normal Dolphin cluster, create a workflow, and add a shell task to the workflow. After the scheduling is normal, stop the worker service process and check the number of times that the task instance is delivered. ### Anything else _No response_ ### Version 3.2.x ### Are you willing to submit PR? - [ ] 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]
