luozenglin opened a new issue, #18098: URL: https://github.com/apache/doris/issues/18098
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Description ## User Interface ### Create resource groups ``` CREATE RESOURCE GROUP group_name PROPERTIES ( "cpu_scheduling_weight"="1", // required, cpu scheduling weight "concurrency_limit"="0" // optional, the number of concurrent queries in the resource group ). ``` * Do not implement resource group nesting and selectors for now, consider scalability. * Create resource group `default` by default, use `default` resource group for queries where the user does not specify a resource group. ### Select resource group User user1 can specify the resource group to be used via session variable: ``` SET resource_group = 'group_name'. ``` Subsequent resource group authentication is required. ### Delete the resource group ``` DROP RESOURCE GROUP 'resource_group_name'. ``` Remove a resource group in fe metadata, without affecting the task being executed in be. ### Modify a resource group ``` ALTER RESOURCE GROUP 'resource_group_name' SET ("cpu_scheduling_weight"="32", "concurrency_limit"="0"); // add or modify resource group attributes ALTER RESOURCE GROUP 'resource_group_name' REMOVE ("concurrency_limit"="0"); // Delete the resource group attribute ``` Modify the resource group information in fe without modifying the be side synchronously. be side needs to check the newly queried resource group information and update the running resource group information. ### Show resource groups ``` SHOW RESOURCE GROUP where xxx; // Show resource group ``` ## Implementation ideas Resource group information is recorded in fe metadata, a unique ID is assigned to each resource group, fe assigns the query to the resource group via a session variable, and sends the query and resource group information to be. ### Use case _No response_ ### Related issues _No response_ ### 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
