The StarRocks kernel supports multi-warehouse functionality, allowing CN (Compute Node) instances to be grouped into different warehouses. This setup enables physical isolation of compute resources. When using KB to manage these, we can consider mapping one warehouse to one KB component. During cluster operation, it may be necessary to dynamically add or remove warehouses (components).
Additionally, the warehouse(component) can be stopped and started independently. However, the OpsRequest only supports cluster-level stop and start operations. To enhance operational flexibility and granular control, it's necessary to support component-level stop and start capabilities.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
If this is a new feature, please describe the motivation and goals.
A clear and concise description of why you want to happen, link the design doc if possible
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
What is the user interaction of your feature
The StarRocks kernel supports multi-warehouse functionality, allowing CN (Compute Node) instances to be grouped into different warehouses. This setup enables physical isolation of compute resources. When using KB to manage these, we can consider mapping one warehouse to one KB component. During cluster operation, it may be necessary to dynamically add or remove warehouses (components).
Additionally, the warehouse(component) can be stopped and started independently. However, the OpsRequest only supports cluster-level stop and start operations. To enhance operational flexibility and granular control, it's necessary to support component-level stop and start capabilities.
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
If this is a new feature, please describe the motivation and goals. A clear and concise description of why you want to happen, link the design doc if possible
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.