AnalyticDB for MySQL Data Lakehouse Edition (V3.0) uses an architecture that separates storage and computing resources to implement elastic scaling of computing resources. You can divide computing resources into different resource groups that physically separate the computing resources, and then associate AnalyticDB for MySQL database accounts with different resource groups. If SQL or Spark jobs are performed by using a specific account, the queries are performed only on the resource group that is associated with the account. The separation between resource groups associated with different accounts allows a cluster to support multiple tenants and hybrid loads.
Interactive resource group and job resource group
AnalyticDB for MySQL resource groups fall into two types based on the job type: interactive resource group and job resource group.
Interactive resource group:
How it works: After you submit a query to a frontend node, the frontend node uses the permanent computing resources of an interactive resource group to execute the query in XIHE MPP mode. The query is responded in milliseconds. For more information about XIHE MPP, see the "XIHE MPP engine" section of the Functions and features topic.
Applicable scenarios: real-time processing scenarios that require high queries per second (QPS) and low response time (RT).
Executed jobs: XIHE MPP SQL queries.
Elastic scaling: Computing resources are scaled in scheduled scaling mode.
Job resource group:
How it works: After you submit a query to a frontend node, the frontend node uses the temporary computing resources of a job resource group to execute the query in XIHE BSP mode. The query is responded in seconds or minutes. The amount of temporary computing resources that can be used varies based on the size of the executed job, ranging from 0 AnalyticDB compute units (ACUs) to the maximum resource amount of the job resource group. For more information about XIHE BSP, see the "XIHE BSP engine" section of the Functions and features topic.
Applicable scenarios: batch processing scenarios that require high throughput.
Executed jobs: XIHE BSP SQL queries, Spark SQL queries, and Spark applications.
Elastic scaling: Computing resources are scaled in on-demand scaling mode.
Default resource group and custom resource group
AnalyticDB for MySQL resource groups fall into two types based on the creation mode: default resource group and custom resource group.
Default resource group
Definition: the default resource group named
user_defaultthat exists when a cluster is created.Properties:
You can modify the amount of reserved computing resources for the default resource group in the range of 0 ACUs to the amount of resources that are not allocated within a cluster in increments of 16 ACUs.
You can change the amount of reserved computing resources for the default resource group.
You cannot delete the default resource group.
The job type of the default resource group is interactive. You cannot change the job type.
You cannot associate the default resource group with a database account.
Custom resource group
Definition: the resource group of the interactive or job type that you create. For information about how to create a resource group, see Create a resource group or CreateDBResourceGroup.
Properties:
You can modify the amount of resources for custom resource groups. For more information, see the "Modify a resource group" section of the Create a resource group topic.
For an interactive resource group, you can modify the amount of reserved computing resources in the range of 16 ACUs to the amount of resources that are not allocated within a cluster in increments of 16 ACUs.
For a job resource group, the minimum amount of computing resources is 0 ACUs. You can modify the maximum amount of computing resources to 1,024 ACUs in increments of 8 ACUs. If you want to modify the amount of resources, submit a ticket.
You can delete custom resource groups.
You cannot change the job type of a custom resource group.
You can associate a custom resource group with or disassociate a custom resource group from a database account. For more information, see Associate with or disassociate from a database account.
You can configure a Thrift server for a job resource group. For more information, see Start and stop a Thrift server.