v-kkhuang opened a new issue, #5415: URL: https://github.com/apache/linkis/issues/5415
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/linkis/issues) and found no similar feature requirement. ### Linkis Component - [ ] linkis-commons - [x] linkis-computation-governance - [ ] linkis-dist - [ ] linkis-engineconn-plugin - [ ] linkis-extensions - [ ] linkis-orchestrator - [ ] linkis-public-enhancements - [ ] linkis-spring-cloud-services - [ ] linkis-web ### Description Currently, Linkis uses a fixed queue configuration for Yarn jobs. This can lead to inefficient resource utilization when some queues are heavily loaded while others have available capacity. Users need the ability to automatically select the optimal queue based on real-time resource usage. ### Steps to reproduce 1. Configure a primary queue and a secondary queue 2. Submit jobs to Linkis 3. Jobs always use the primary queue even when it's heavily loaded 4. Secondary queue capacity is wasted ### Expected behavior Linkis should automatically select the optimal queue based on: - Resource usage threshold (configurable) - Support for multiple engines (Spark, etc.) - Support for specific Creator types - Automatic fallback to primary queue if secondary queue is unavailable or overloaded ### Your environment - Linkis version used: 1.18.0 - Environment name and version: - hadoop-3.3.4 - spark-2.4.3 - scala-2.11.12 - jdk 1.8.0_xxx ### Anything else This feature enables intelligent queue selection to optimize resource utilization and improve job performance. ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
