advancedxy opened a new issue, #412: URL: https://github.com/apache/incubator-uniffle/issues/412
### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) ### Search before asking - [X] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues. ### What would you like to be improved? After the https://github.com/apache/incubator-uniffle/issues/405 is finished, shuffle server would report its capability to coordinator, such as - disk quota - disk iops(by HDD/SSD) - disk number - server thread number etc. The coordinator should support such mixed deployments, and assign workload based on shuffle worker's capability. In this way, one uniffle cluster could scale up to handle more traffic with commodity servers and also support high priority apps with specialized hardware, such as server with SSD disks. ### How should we improve? - implement new assignment strategy to support: - more affinity settings: such as prefer, required semantics - load awareness assignments - necessary changes to modify corresponding RPC interfaces. ### Are you willing to submit PR? - [ ] 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: dev-unsubscr...@uniffle.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
