All Products
Search
Document Center

PolarDB:Create a PolarDB-X instance

Last Updated:May 19, 2025

This topic describes how to create a PolarDB-X instance.

Procedure

  1. Log on to the PolarDB-X console.

  2. In the top navigation bar, select the region where the instance is deployed.

  3. On the Instances page, click the PolarDB-X 2.0 tab.

  4. In the upper-right corner of the page, click Create Instance.

  5. On the buy page, configure the parameters. The following table describes the parameters.

    Parameter

    Description

    Product Type

    The PolarDB-X instance type that you want to create. Valid values:

    • PolarDB-X 2.0 Prepay

    • PolarDB-X 2.0 Postpay

    • PolarDB-X 1.0 (Subscription)

    Note
    • If you select the prepay (subscription billing) type, you are charged for the resource usage of the PolarDB-X instance when you purchase the instance. This type is suitable for long-term usage and is more cost-effective than the postpay (pay-as-you-go billing) type.

    • If you select the postpay (pay-as-you-go billing) type, you are charged for the resource usage of the PolarDB-X instance on an hourly basis. This type is suitable for short-term usage. You can release it if you no long require it to reduce costs.

    • To create a pay-as-you-go PolarDB-X instance, make sure that the balance in your Alibaba Cloud account is greater than or equal to USD 100.

    Regions and Zones

    The region in which you want to deploy the PolarDB-X instance.

    Create Type

    The method that you want to use to create the PolarDB-X instance.

    • Create by Default: creates the PolarDB-X instance.

    • Migrate from ApsaraDB RDS: migrates data from an existing RDS instance to the PolarDB-X instance.

      • Source RDS Version: the version of the source RDS instance. Valid values: MySQL 5.6, MySQL 5.7, and MySQL 8.0.

      • Source RDS Instance: the source RDS instance. Select an existing RDS instance.

    Topology

    The deployment topology of the instance nodes. Valid values:

    • Single-zone Deployment: You only need to specify a zone for the primary node. The secondary and logger nodes are automatically deployed in the same zone as the primary node.

    • Three-zone Deployment: You need to specify different zones for the primar, secondary, and logger nodes. This topology enables disaster recovery across zones without additional charges.

    Primary Node Zone

    The zone in which you want to deploy the primary node.

    Secondary Node Zone

    The zone in which you want to deploy the secondary nodes. This parameter is available only after you set the Topology parameter to Three-zone Deployment.

    Logger Node Zone

    The zone in which you want to deploy the logger nodes. This parameter is available only after you set the Topology parameter to Three-zone Deployment.

    Network Type

    The network type of the instance. By default, the value is VPC.

    VPC

    The VPC of the PolarDB-X instance.

    Note
    • If you do not have an existing VPC, create one. The VPC must be in the same region and zone as the PolarDB-X instance.

    • If you want to access the PolarDB-X instance from an ECS instance, make sure that the ECS instance and the PolarDB-X instance are in the same VPC. After a PolarDB-X instance is created, you cannot change its VPC.

    vSwitch

    The vSwitch of the instance.

    Note
    • If you do not have an existing vSwitch, create one.

    • If you want to access the PolarDB-X instance from an ECS instance, make sure that the ECS instance and the PolarDB-X instance are in the same VPC.

    Compatibility

    Valid values: MySQL 5.7 and MySQL 8.0.

    Edition

    The edition of the instance. Valid values: Standard Edition (centralized) and Enterprise Edition (distributed).

    Instance Purchase Type

    • If Edition is set to Enterprise Edition, this parameter is set to User Defined.

    • If Edition is set to Standard Edition, this parameter is set to Default.

    Instance Family

    Valid values: General-purpose and Dedicated.

    • General-purpose: The instance shares idle computing resources such as CPUs with other instances on the same server. This enhances cost efficiency.

    • Dedicated: The instance does not share allocated compute resources such as CPUs with other instances on the same server. This improves the reliability and stability of the cluster.

    CN Node Spec

    The compute node specifications of the instance. Compute nodes provide a distributed SQL engine that contains core optimizers and executors. Compute nodes provide a stateless SQL engine for distributed routing and computing. The nodes use the two-phase commit protocol (2PC) to coordinate distributed transactions, execute DDL statements in a distributed manner, and maintain global indexes.

    DN Node Spec

    The data node specifications of the instance. Data nodes provide a data storage engine. Data nodes use the majority-based Paxos consensus protocol to provide highly reliable storage services and use multiversion concurrency control (MVCC) for distributed transactions. Data nodes also provide the pushdown computation feature for operators such as Project, Filter, Join, and Agg in distributed systems, and support local SSDs and shared storage.

    CN Nodes

    The number of compute nodes.

    DN Nodes

    The number of data nodes.

    Node Specifications

    The node specifications. This parameter is available only if you set Edition to Standard Edition.

    Storage Type

    The storage type of the instance. Valid values:

    • Local SSD-Custom.

    • Local SSD

      Note

      You do not need to specify the storage space size for the instance. The system charges you based on the actual disk space you use on an hourly basis (any usage less than one hour is rounded up to a full hour).

    Storage Node Disk

    The size of a single data node. This parameter is available only if you set Storage Type to Local SSD-Custom.

    Quantity

    The number of instances that you want to purchase.

    Subscription Duration

    The subscription duration of the instance. This parameter is available only if you select the subscription instance type.

    Note

    You can select Auto-renewal. Then, the instance is automatically renewed before it expires.

  6. Click Buy Now.

  7. On the Confirm Order page, read and agree to the terms of service and click Pay to complete the payment.

  8. After you complete the payment, wait until the system creates the instance. The creation process requires 10 to 15 minutes to complete. After the instance is created, you can go to the Instance List page in the PolarDB-X console to view the instance that you created.