AnalyticDB for MySQL provides the resource group isolation feature that allows you to schedule computing jobs based on priorities and classify different queries. This ensures that your core business is not affected by complex computing and unexpected events and that resources can be properly allocated to maximize cluster performance. You can create, modify, or delete resource groups in the AnalyticDB for MySQL console or by calling API operations.
Prerequisites
An AnalyticDB for MySQL Data Lakehouse Edition cluster is created.
Create a resource group
Create an interactive resource group
Log on to the AnalyticDB for MySQL console. In the upper-left corner of the console, select a region. In the left-side navigation pane, click Clusters. On the Data Lakehouse Edition tab, find the cluster that you want to manage and click the cluster ID.
In the left-side navigation pane, choose Cluster Management > Resource Management. On the Resource Management page, click the Resource Groups tab.
In the upper-right corner of the tab, click Create Resource Group. In the Create Resource Group panel, configure the parameters that are described in the following table.
Parameter
Description
Resource Group Name
The name of the resource group. The name must be 2 to 30 characters in length and can contain only letters, digits, and underscores (_). The name must start with a letter.
Job Type
The job type of the resource group. Select Interactive from the drop-down list. Interactive resource groups are suitable for real-time processing scenarios that require high queries per second (QPS) and low response time (RT). In these scenarios, you can use scheduled scaling to scale computing resources.
Database Engine
The database engine used by the resource group. Valid values: Xihe and Spark.
Xihe: The resource group supports only XIHE SQL queries.
Spark: The resource group supports only Spark jobs. Spark jobs are run in an interactive manner.
ImportantThis parameter is in invitational preview. To use this parameter, join the AnalyticDB for MySQL DingTalk group 33600023146.
Cluster Size
The size of a single compute cluster. Unit: AnalyticDB compute units (ACUs). The minimum value is 16 ACUs.
Minimum Clusters
The minimum number of compute clusters that you must run in the resource group. The value must be less than or equal to the maximum number of compute clusters. The minimum value is 1.
If you set the Minimum Clusters and Maximum Clusters parameters to different values, AnalyticDB for MySQL dynamically scales the amount of computing resources available for the resource group within the range of the minimum and maximum values based on query loads.
If you set the Minimum Clusters and Maximum Clusters parameters to the same value, the value must be greater than or equal to 2. After the resource group is created, AnalyticDB for MySQL starts the specified compute clusters to statically control the total amount of computing resources available for the resource group.
Maximum Clusters
The maximum number of compute clusters that you can run in the resource group. The maximum value is 10.
If you set the Minimum Clusters and Maximum Clusters parameters to different values, AnalyticDB for MySQL dynamically scales the amount of computing resources available for the resource group within the range of the minimum and maximum values based on query loads.
If you set the Minimum Clusters and Maximum Clusters parameters to the same value, the value must be greater than or equal to 2. After the resource group is created, AnalyticDB for MySQL starts the specified compute clusters to statically control the total amount of computing resources available for the resource group.
Click OK.
Create a job resource group
Log on to the AnalyticDB for MySQL console. In the upper-left corner of the console, select a region. In the left-side navigation pane, click Clusters. On the Data Lakehouse Edition tab, find the cluster that you want to manage and click the cluster ID.
In the left-side navigation pane, choose Cluster Management > Resource Management. On the Resource Management page, click the Resource Groups tab.
In the upper-right corner of the tab, click Create Resource Group. In the Create Resource Group panel, configure the parameters that are described in the following table.
Parameter
Description
Resource Group Name
The name of the resource group. The name must be 2 to 30 characters in length and can contain only letters, digits, and underscores (_). The name must start with a letter.
Job Type
The job type of the resource group. Select Job from the drop-down list. Job resource groups are suitable for batch processing scenarios that require high throughput. In these scenarios, you can use on-demand scaling to scale computing resources.
Minimum Computing Resources
The minimum amount of computing resources. Set the value to 0 ACUs.
Maximum Computing Resources
The maximum amount of computing resources. Configure this parameter in the range of 8 ACUs to 1,024 ACUs in increments of 8 ACUs. The maximum amount of computing resources that can be configured in the console is 1,024 ACUs. If you want to modify the amount of resources, submit a ticket.
Spot Instance
Specifies whether to enable the spot instance feature for the resource group.
After you enable the spot instance feature, Spark jobs that run in the job resource group attempt to use the spot instance resources. For more information, see Spot instances.
Click OK.
Modify a resource group
After you create a resource group, you can modify the resource amount settings, and enable or disable the spot instance or multi-cluster feature for the resource group. To modify a resource group, perform the following steps:
On the Resource Groups tab, find the resource group that you want to modify and click Modify in the Actions column.
In the Modify Resource Group panel, modify the resource amount settings, and enable or disable the spot instance or multi-cluster feature for the resource group.
Click OK.
You cannot change the job type for resource groups of Data Lakehouse Edition clusters.
The modification to the amounts of reserved computing resources and maximum computing resources takes effect in real time.
You cannot enable the multi-cluster feature for existing interactive resource groups.