This topic describes how to create a cluster in the AnalyticDB for MySQL console.

Create a Data Warehouse Edition (V3.0) cluster

  1. Log on to the AnalyticDB for MySQL console.
  2. In the upper-left corner of the page, select the region where the cluster resides.
  3. In the left-side navigation pane, click Clusters.
  4. In the upper-right corner of the Data Warehouse Edition (V3.0) tab, click Create Cluster.
  5. Set the Product Type parameter to Subscription or Pay-as-you-go.
    • Pay-as-you-go: You are charged on an hourly basis for the resources that you use. This billing method is suitable for short-term usage. To reduce costs, you can release pay-as-you-go clusters when they are no longer needed.
    • Subscription: You must pay an upfront subscription fee when you create subscription clusters. For long-term usage, this billing method is more cost-effective than the pay-as-you-go billing method. You are charged lower prices for longer subscription periods.
  6. Configure the parameters that are described in the following table and click Buy Now in the lower-right corner.
    ParameterFeature
    VersionThe edition and version of the cluster. Select Data Warehouse Edition (V3.0).
    RegionThe region where you want to create the cluster. After the cluster is created, the region cannot be changed. To maximize the cluster access speed, we recommend that you select a region that is closest to the geographic area of your business.
    ZoneThe zone where you want to create the cluster. Each zone is an independent physical location within a region. Zones in the same region do not have substantial differences.
    Network TypeThe network type of the cluster. This parameter is automatically set to VPC. You do not need to specify this parameter.

    A virtual private cloud (VPC) is an isolated network environment that provides enhanced security.

    VPC

    VSwitch

    		The VPC in which the cluster resides. Make sure that the AnalyticDB for MySQL cluster and the Elastic Compute Service (ECS) instance you want to connect to the cluster are deployed in the same VPC. Otherwise, the cluster and the ECS instance cannot communicate over a private network or achieve optimal performance.
    • If you have created a VPC that meets your business requirements, select the VPC. For example, if you have created an ECS instance in a VPC that meets your business requirements, select the VPC.
    • Otherwise, use the default VPC and vSwitch. For more information, see Default VPCs and default vSwitches.
    • If the default VPC and vSwitch cannot meet your business requirements, you can create your own VPC and vSwitch. For more information, see Create and manage a VPC.
    Version Upgrade PolicyThe policy that is used to upgrade the cluster version. The cluster is automatically upgraded to the latest version within a specified maintenance window. The default maintenance window is from 12:00 to 13:00. After you create a cluster, you can specify a maintenance window for the cluster. For more information, see Configure a maintenance window.
    ModeThe mode of the cluster. Valid values: Elastic Mode and Reserved Mode. For more information about the differences between the modes, see the "FAQ" section of the Editions topic.
    Edition The edition of the cluster. The following editions are supported:
    • If you select Elastic Mode, the Edition parameter is automatically set to Elastic Cluster. You do not need to specify this parameter.

      Elastic Mode for Cluster Edition uses a decoupled architecture that separates computing resources from storage resources to provide capabilities such as elastic scaling, multi-tenant isolation, storage separation of cold and hot data, heterogeneous storage, and user programming. This implements flexible real-time analysis with high performance at low resource costs.

    • If you select Reserved Mode, the Edition parameter is automatically set to Reserved Cluster. You do not need to specify this parameter.

      Reserved Mode for Cluster Edition uses a high-availability architecture that consists of three replicas to provide data reliability required in the finance industry. You can scale out nodes and scale up storage within seconds for reserved clusters. This allows you to read and write data in real time with higher throughput.

    Note The available editions vary based on the region that you select. For more information, see Editions.
    Instance TypeThe instance type of the cluster. The following instance types are supported:
    • If you select Elastic Mode, the Instance Type parameter is automatically set to E32. You do not need to specify this parameter.
    • If you select Reserved Mode, the Instance Type parameter can be set to C8 or C32.

    For more information, see Editions.

    Computing ResourcesThe computing resources of the cluster. Computing resources are used for data computing. The increase of computing resources can speed up data queries.
    Note This parameter is available only if the Mode parameter is set to Elastic Mode.
    ESSD Performance LevelThe enhanced SSD (ESSD) performance level of the cluster. This parameter is automatically set to PL1. As your business needs evolve, you can change the ESSD performance level by scaling your cluster. For more information, see Change cluster configurations (Data Warehouse Edition).
    EIU CapacityThe single-node specifications of an elastic I/O unit (EIU) for an elastic cluster. This parameter is automatically set to 8 cores and 64 GB. Each EIU consists of three nodes and has 24 cores and 192 GB memory.

    Elastic I/O resources are bundled into units and sold as EIUs. You can use EIUs to individually scale up storage resources for clusters in Elastic mode for Cluster Edition. For more information, see Use EIUs to scale up storage resources.

    Note You can specify this parameter only if the Mode parameter is set to Elastic Mode and the Computing Resources parameter is set to 32 Cores and 128 GB or more.
    EIUsThe number of EIUs that are required for data storage. You can specify this parameter based on the storage performance metrics of EIUs. For more information, see the "EIU-based storage performance metrics" section of the Use EIUs to scale up storage resources topic. Alternatively, you can purchase one EIU when you create a cluster, and then scale up your elastic I/O resources when needed. For more information, see Change cluster configurations (Data Warehouse Edition).
    Note You can specify this parameter only if the Mode parameter is set to Elastic Mode and the Computing Resources parameter is set to 32 Cores and 128 GB or more.
    Hot Data Storage Space Description

    Cold Data Storage Space Description

    		You are charged for the actual amount of storage occupied by hot and cold data. You do not need to purchase storage in advance. The following section describes hot and cold data:
    • Hot data refers to data that is frequently accessed. Hot data is stored in ESSDs to provide high I/O performance and deliver high-performance access.
    • Cold data refers to data that is infrequently accessed. Cold data is cost-effective because it is stored in HDDs.

    For more information, see Separation of hot and cold data storage.

    Note This parameter is available only if the Mode parameter is set to Elastic Mode.
    Node GroupsThe number of node groups. By default, each node group consists of three nodes.
    Note This parameter is available only if the Mode parameter is set to Reserved Mode.
    CapacityThe storage capacity of a single node group. If you purchase multiple node groups, you can use the following formula to calculate the total storage capacity of the cluster: Total storage capacity = Storage capacity per node group × Number of node groups.
    Note This parameter is available only if the Mode parameter is set to Reserved Mode.
    Disk EncryptionAnalyticDB for MySQL provides the disk encryption feature. After this feature is enabled, the system encrypts the data on each disk of your cluster based on Elastic Block Storage (EBS). This way, your data cannot be decrypted even if it is leaked.
    Note
    • The first time you enable Disk Encryption, you must create a service-linked role by clicking Create Service Linked Role and select a key from the Key drop-down list. For more information, see Disk encryption.
    • The disk encryption feature can be enabled for an AnalyticDB for MySQL cluster only when you are creating the cluster.
    • This feature cannot be disabled after the cluster is created.
    • After you enable the disk encryption feature, this feature is automatically enabled for snapshots of reserved clusters and reserved clusters created from the snapshots.
    • Key Management Service (KMS) is required if you want to enable the disk encryption feature. When you use KMS, you are charged for key management and API calls. For more information, see Billing of KMS.
    DurationThe subscription duration of the cluster.
    Note This parameter is available only if the Product Type parameter is set to Subscription.
  7. Complete the subsequent operations based on the specified Product Type parameter.
    • Subscription
      1. On the Confirm Order page, confirm your order information. Read and select the Terms of Service. Then, click Pay.
      2. On the Purchase page, confirm the order and the payment method, and click Purchase.
    • Pay-as-you-go

      On the Confirm Order page, confirm your order information. Read and select the Terms of Service. Then, click Activate Now.

    Note After you complete the payment, it takes about 20 minutes to create the cluster. Then, the newly created cluster is displayed on the Data Warehouse Edition (V3.0) tab.

Create a Data Lakehouse Edition (V3.0) cluster

  1. Log on to the AnalyticDB for MySQL console.
  2. In the upper-left corner of the page, select the region where the cluster resides.
  3. In the left-side navigation pane, click Clusters.
  4. In the upper-right corner of the Data Lakehouse Edition (V3.0) tab, click Create Cluster.
  5. Set the Product Type parameter to Subscription or Pay-as-you-go.
    • Pay-as-you-go: You are charged on an hourly basis for the resources that you use. This billing method is suitable for short-term usage. To reduce costs, you can release pay-as-you-go clusters when they are no longer needed.
    • Subscription: You must pay an upfront subscription fee when you create subscription clusters. For long-term usage, this billing method is more cost-effective than the pay-as-you-go billing method. You are charged lower prices for longer subscription periods.
  6. Configure the parameters that are described in the following table and click Buy Now in the lower-right corner.
    ParameterFeature
    VersionThe edition and version of the cluster. Select Data Lakehouse Edition (V3.0).
    RegionThe region where you want to create the cluster. After the cluster is created, the region cannot be changed. To maximize the cluster access speed, we recommend that you select a region that is closest to the geographic area of your business.
    ZoneThe zone where you want to create the cluster. Each zone is an independent physical location within a region. Zones in the same region do not have substantial differences.
    Network TypeThe network type of the cluster. This parameter is automatically set to VPC. You do not need to specify this parameter.

    A VPC is an isolated network environment that provides enhanced security.

    VPC

    VSwitch

    		The VPC in which the cluster resides. Make sure that the AnalyticDB for MySQL cluster and the ECS instance you want to connect to the cluster are deployed in the same VPC. Otherwise, the cluster and the ECS instance cannot communicate over a private network or achieve optimal performance.
    • If you have created a VPC that meets your business requirements, select the VPC. For example, if you have created an ECS instance in a VPC that meets your business requirements, select the VPC.
    • Otherwise, use the default VPC and vSwitch. For more information, see Default VPCs and default vSwitches.
    • If the default VPC and vSwitch cannot meet your business requirements, you can create your own VPC and vSwitch. For more information, see Create and manage a VPC.
    Version Upgrade PolicyThe policy that is used to upgrade the cluster version. The cluster is automatically upgraded to the latest version within a specified maintenance window. The default maintenance window is from 10:00 to 11:00. After you create a cluster, you can specify a maintenance window for the cluster. For more information, see Configure a maintenance window.
    Reserved Computing Resources

    The reserved computing resources of the cluster. Reserved computing resources are used for data computing and can be allocated to interactive and job resources groups. The increase of computing resources can speed up data queries. For information about resource groups, see Resource group overview.

    Valid values: 0 to 512. Unit: AnalyticDB compute units (ACUs). The value must be in increments of 16 ACUs.
    • If you set this parameter to 0, you can create only job resource groups.
    • If you set this parameter to a value greater than 0, you can create interactive and job resource groups.

    As your business needs evolve, you can purchase more reserved computing resources by scaling your cluster. For more information, see Change cluster configurations (Data Lakehouse Edition).

    Default Allocation BehaviorSpecifies whether all the reserved computing resources are allocated to the default resource group.

    If you want to load a built-in dataset, select Yes because the loading process occupies the reserved computing resources of the user_default resource group.

    Reserved Storage ResourcesThe reserved storage resources of the cluster. Reserved storage resources are used for data storage. Up to 4 TB of hot data can be stored.

    Valid values: 0 to 4800. Unit: ACUs. The value must be in increments of 24 ACUs.

    A built-in dataset occupies about 10 GB of hot data storage. If you want to load a built-in dataset to the cluster, purchase at least 24 ACUs of reserved storage resources. For more information about the built-in dataset, see Manage a built-in dataset.

    You cannot scale down the reserved storage resources of a Data Lakehouse Edition (V3.0) cluster to 0 ACUs. You can set the amount of reserved storage resources to 0 ACUs when you create a cluster, and then scale up your reserved storage resources when needed. For more information, see Change cluster configurations (Data Lakehouse Edition).

  7. Complete the subsequent operations based on the specified Product Type parameter.
    • Subscription
      1. On the Confirm Order page, confirm your order information. Read and select the Terms of Service. Then, click Pay.
      2. On the Purchase page, confirm the order and the payment method, and click Purchase.
    • Pay-as-you-go

      On the Confirm Order page, confirm your order information. Read and select the Terms of Service. Then, click Activate Now.

    Note After you complete the payment, it takes about 20 minutes to create the cluster. Then, the newly created cluster is displayed on the Data Lakehouse Edition (V3.0) tab.