Aer1208 opened a new issue #7918: URL: https://github.com/apache/dolphinscheduler/issues/7918
### 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 Restart the cluster, and the running tasks will be resumed for 2 times ### What you expected to happen Restart the cluster, and the running tasks will be resumed once ### How to reproduce 1、The cluster has a running Flink real-time task 2、Execute stop-all.sh 3、Execute start-all.sh 4、The cluster has two running Flink real-time tasks ### Anything else I analyze stop-all.sh. The sequence of stopping the service is master server, work server, logger server, alert server and API server. If the master server is stopped first, the running job status of the work server cannot be repaired from the running status to the status to be recovered. Then restart the cluster, and there will be two running tasks to be recovered. Therefore, after the work server is stopped, stopping the master server can ensure that the running tasks can be resumed only once. ### Version 1.3.9 ### 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]
