AnalyticDB for MySQL Data Warehouse Edition (V3.0) in Elastic mode for Cluster Edition utilizes 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 isolate the computing resources, and then associate AnalyticDB for MySQL database accounts with different resource groups. If SQL queries are performed by using a specific account, the queries are performed only on the resource group that is associated with the account. The isolation between resource groups associated with different accounts allows a cluster to support multiple tenants and hybrid loads.

Classification of resource groups

Default resource group

  • Definition: the default resource group named USER_DEFAULT that exists when a cluster is created.
  • Properties:
    • Computing resources are exclusive and must be in increments of 16 cores and 64 GB memory, which are equivalent to the resource amount of one compute node. The amount of computing resources can be configured in the range of 0 cores and 0 GB memory to the total amount of computing resources within a cluster.
    • You cannot delete the default resource group.
    • Computing resources that are not allocated to custom resource groups belong to the default resource group. You cannot change the amount of resources for the default resource group.
    • The default query type is Default_Type. You can change the query type. For more information about how to change a query type, see Modify a resource group. For more information about query types, see Query execution modes.
    • AnalyticDB for MySQL database accounts that are not associated with custom resource groups are associated with the default resource group.

Custom resource group

  • Definition: the resource group of the Default_Type, batch, or interactive type that you create. For more information about how to create a resource group, see Create a resource group or CreateDBResourceGroup.
  • Properties:
    • Computing resources are exclusive and must be in increments of 16 cores and 64 GB memory, which are equivalent to the resource amount of one compute node. The amount of computing resources can be configured in the range of 0 cores and 0 GB memory to the total amount of computing resources within a cluster.
    • You can delete custom resource groups.
    • You can change the amount of resources for a custom resource group.
    • You can change the query type. For more information about how to change a query type, see Modify a resource group. For more information about query types, see Query execution modes.
    • You can associate a resource group with or disassociate a resource group from a database account. For more information, see Associate with or disassociate from a database account.

Scenarios

Resource groups are suitable for different scenarios based on their query types.
  • Default_Type: Resource groups of this type follow the query type of the cluster.
  • Batch: suitable for large-volume queries that require a long period of time to execute, such as extract-transform-load (ETL) queries.
  • Interactive: suitable for real-time analysis queries that require low latency.

References

Specify a resource group to execute queries