173lyb opened a new issue, #15762: URL: https://github.com/apache/dolphinscheduler/issues/15762
### 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 task is set to wait in series, scheduled every five minutes, and the task itself is executed for sometimes 3 minutes, sometimes exactly five minutes, and sometimes 6 minutes, which will cause subsequent tasks to be queued, but perhaps because the scheduling interval is too short, this phenomenon will occur: the queued tasks are not executed, are blocked all the time, and cannot be stopped. ### What you expected to happen After my observation, it is possible that the last task just finished, and the next queued task just started at this time. During this period, there is a problem in obtaining the status of the task instance, which may be caused by some thread locks. ### How to reproduce You can set up a 5-minute task, set a shell script to sleep randomly for 3-6 minutes, and let him run all night, so that there will be a lot of tasks queued the next day to see if they are executed properly. ### Anything else There is no problem that all the other tasks are waiting in series. There is only five minutes to schedule these tasks. There will be bug like this. ### Version 3.1.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]
