lhjzmn opened a new issue #8951: URL: https://github.com/apache/dolphinscheduler/issues/8951
### 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 I upgraded from version 1.3.8 to 2.0.5, worker resources were exhausted due to too many tasks submitted by users。 ### Use case I looked through the source code and saw that in MasterConfig 1.3.8, there is a parameter masterExecTaskNum with a value of 20, that is, only 20 tasks can be submitted to the worker for execution at the same time. After upgrading to 2.0.5, although this parameter exists, it is not used. The master will rudely submit tasks to the workers for execution. I don't understand why it is designed this way. This problem is fatal in production. I think the number of tasks running at the same time should be controlled, like version 1.3.8, to ensure that the pressure on the workers is not too high, even at the tenant level (ie each tenant can run at most N jobs at the same time) ### Related issues _No response_ ### 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]
