fishhami opened a new issue, #14813: URL: https://github.com/apache/dolphinscheduler/issues/14813
### 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 [version] 3.1.7 [description] I created a task group, set the resource capacity to 2, and created 6 tasks at the same time.2 tasks will start to execute, and 4 tasks are in the status of submitted successfully. But when those two tasks are executed, the task group resources are in an idle state at this time, and the four tasks that were submitted successfully before are not scheduled for execution, and have always been submitted successfully. Then I create a new task, this task can obtain the task group resources and start executing。 ### What you expected to happen When the task group resources are free, the tasks in the queue should be scheduled and executed normally instead of being blocked. ### How to reproduce <img width="1424" alt="image" src="https://github.com/apache/dolphinscheduler/assets/54088190/364f9690-fbe9-4dbb-9160-6bd1bee3e15b";> <img width="1105" alt="image" src="https://github.com/apache/dolphinscheduler/assets/54088190/1436b22f-a519-4f55-8d8b-9c09ce20a6cc";> From the above, we can see that the 'data-analysis' task group has idle resources, but there are still 4 tasks in the WAIT_QUEUE state, and they are not scheduled for execution. I don't know if there is a queuing timeout? Because during the test, I found that if the task group can release resources quickly, the tasks in the queue can be scheduled for execution. But when the previous task takes a long time, it will appear that although the resources are finally released , the previously queued tasks will no longer continue to be scheduled for execution ### Anything else _No response_ ### 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]
