All Products
Search
Document Center

AnalyticDB for MySQL:Create a Data Warehouse Edition cluster

Last Updated:Sep 05, 2023

This topic describes how to create a Data Warehouse Edition (V3.0) cluster in the AnalyticDB for MySQL console.

Create a Data Warehouse Edition (V3.0) cluster

  1. Log on to the AnalyticDB for MySQL console. In the upper-right corner of the console, click Buy Cluster.

  2. Select an option for the Product Type parameter.

    • 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.

  3. Configure the parameters that are described in the following table.

    Parameter

    Description

    Version

    The edition and version of the cluster. Select Data Warehouse Edition (V3.0).

    Region

    The region where you want to create the cluster. After a cluster is created, you cannot change the region of the cluster. To maximize the cluster access speed, we recommend that you select a region that is geographically closest to your business.

    Zone

    The 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.

    VPC

    VSwitch

    • If you have created a virtual private cloud (VPC) that meets your business requirements, select the VPC. For example, if you have created an Elastic Compute Service (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 a VPC and a vSwitch. For more information, see Create and manage a VPC.

    Important

    If you use other Alibaba Cloud services such as ECS and ApsaraDB RDS, make sure that your AnalyticDB for MySQL cluster resides in the same VPC as your ECS and ApsaraDB RDS instances. If your cluster and instances reside in different VPCs, your cluster cannot communicate with your instances over an internal network to achieve optimal performance.

  4. Set the Mode parameter to Elastic Mode or Reserved Mode, configure the corresponding parameters, and then click Buy now in the lower-right corner of the page. In this example, select Elastic Mode.

    Parameter

    Description

    Edition

    For Elastic Mode, the Edition parameter is automatically set to Elastic Cluster.

    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.

    Instance Type

    The Instance Type of the cluster. The parameter is automatically set to E32.

    Disk Encryption

    If you select Disk Encryption, the system encrypts data on each data disk of your cluster based on Elastic Block Storage (EBS). This way, your data cannot be decrypted even if it is leaked.

    The first time you use the disk encryption feature, select Disk Encryption and click Create Service Linked Role to create a service-linked role. Then, select a key from the Key drop-down list. For more information, see Disk encryption.

    Important
    • You can enable the disk encryption feature for an AnalyticDB for MySQL cluster only when you create the cluster.

    • You cannot disable the disk encryption feature after it is enabled.

    • The disk encryption feature requires Key Management Service (KMS). When you use KMS, you are charged for key management and API calls. For more information, see Billing of KMS.

    Computing Resources

    The computing resources of the cluster. You can use computing resources to compute data. The increase in the amount of computing resources can accelerate data queries.

    If you select computing resources of 32 cores or more, you can use the computing resources for hot and cold data separation, resource groups, and elastic resource scaling.

    ESSD Performance Level

    The enhanced SSD (ESSD) performance level of the cluster. Valid values: PL0 and PL1. Default value: PL1. You can scale up the cluster to change the ESSD performance level based on your business requirements. For more information, see Scale up or down a Data Warehouse Edition cluster and change the cluster mode.

    EIU Capacity

    The single-node specifications of an elastic I/O unit (EIU) for clusters in elastic mode for Cluster Edition. This parameter is automatically set to 8Core64GB. Each EIU consists of three nodes and has 24 cores and 192 GB memory (8 cores × 3 and 64 GB × 3).

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

    EIUs

    The number of EIUs that are required to store data. You can configure 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 based on your business requirements. For more information, see Scale up or down a Data Warehouse Edition cluster and change the cluster mode.

    Note

    The EIUs parameter takes effect only when the Computing Resources parameter is set to 32 Cores and 128 GB or higher specifications.

  5. Perform the subsequent purchase operations as prompted based on the Product Type parameter that you selected.

    Approximately 20 minutes after you complete the payment, you can view the cluster on the Data Warehouse Edition (V3.0) tab of the Clusters page.