This topic describes how to create a PolarDB-X instance.
Procedure
Log on to the PolarDB-X console.
In the top navigation bar, select the region where the instance is deployed.
On the Instances page, click the PolarDB-X 2.0 tab.
In the upper-right corner of the page that appears, click Create New Instance.
On the buy page, configure the parameters. The following table describes the parameters.
Parameter
Description
Product Type
The billing method of the PolarDB-X instance. You can set this parameter to PolarDB-X 2.0 (Subscription) or PolarDB-X 2.0 (Pay-as-you-go).
NoteIf you select the subscription billing method, you are charged for the resource usage of the PolarDB-X instance when you purchase the instance. This billing method is suitable for long-term usage because subscription PolarDB-X instances are more cost-effective than pay-as-you-go PolarDB-X instances.
If you select the pay-as-you-go billing method, you are charged for the resource usage of the PolarDB-X instance on an hourly basis. This billing method is suitable for short-term usage. If you no longer require specific pay-as-you-go instances, you can release the instances to reduce costs.
If you want to create a PolarDB-X instance that uses the pay-as-you-go billing method, 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 nodes. Valid values:
Single-zone Deployment: If you select this deployment mode, you must specify a zone for the primary node of the instance. The secondary nodes and logger nodes of the instance are automatically deployed in the same zone as the primary node.
Three-zone Deployment: If you select this deployment mode, you must specify three zones for the instance. The compute nodes, data nodes, Global Meta Service (GMS) nodes, and Change Data Capture (CDC) nodes of the instance are deployed in the specified zones. This deployment mode supports cross-zone disaster recovery. For more information, see Overview.
NoteIf you select Three-zone Deployment, you must specify different values for the Primary Node Zone, Secondary Node Zone, and Logger Node Zone parameters.
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 displayed 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 displayed only after you set the Topology parameter to Three-zone Deployment.
Network Type
The network type of the instance. The value of this parameter is automatically set to VPC and cannot be changed.
NoteBefore you configure the VPC parameter, make sure that a virtual private cloud (VPC) and a vSwitch are created in the region and zones in which you want to deploy the instance. For more information, see Create and manage a VPC.
If you want to access the PolarDB-X instance from an ECS instance, make sure that the PolarDB-X instance and the ECS instance are deployed in the same VPC. After the instance is created, the VPC cannot be changed.
VPC
The VPC in which you want to deploy the PolarDB-X instance.
NoteMake sure that the PolarDB-X instance is in the same VPC as the ECS instance from which you want to access the PolarDB-X instance. To create a VPC, go to the VPC page in the VPC console.
vSwitch
The vSwitch to which you want to connect the instance.
NoteMake sure that the PolarDB-X instance is in the same VPC as the ECS instance from which you want to access the PolarDB-X instance. To create a vSwitch, go to the vSwitch page in the VPC console.
MySQL Version
The engine version of the instance. Valid values: 5.7 and 8.0.
Instance Family
The instance family of the instance. Valid values: Dedicated, Dedicated Host, and General-purpose. For more information, see Instance types.
NoteIf you select the pay-as-you-go billing method, this parameter is unavailable.
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.
NoteThis option is available only if you select Custom as the instance model.
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.
NoteThis option is available only if you select Custom as the instance model.
CN Nodes
The number of compute nodes.
NoteThis option is available only if you select Custom as the instance model.
DN Nodes
The number of data nodes.
NoteThis option is available only when you select Custom as the instance model.
Node Specifications
The number of CPU cores and the memory size of the nodes of the instance. PolarDB-X calculates the price of the instance based on the number and specifications of the nodes. For more information, see Instance types.
NoteIf you select Default as the instance model, the specifications of compute nodes are the same as the specifications of data nodes. If you select Custom as the instance model, you can specify different specifications for compute nodes and data nodes.
Nodes
The number of nodes.
NoteValid values: 2 to 99. If you select Default as the instance model, the number of compute nodes of each instance is the same as the number of data nodes of each instance. If you select Custom as the instance model, you can specify different values for the Nodes parameter for compute nodes and data nodes.
Storage Type
The storage type of the instance. The value of this parameter is automatically set to Local SSD and cannot be changed.
Storage Cost
By default, the storage capacity of each node in the Dedicated Host instance family is 6 TB, and the storage capacity of each node in other instance families is 3 TB. You do not need to specify a storage capacity when you purchase the instance. You are charged based on your actual storage usage on an hourly basis.
Quantity
The number of read-only instances that you want to purchase.
Subscription Duration
The subscription duration of the instance.
NoteThis parameter is displayed only if you use the subscription billing method.
If you select Auto-renewal, the instance is automatically renewed before it expires.
Click Buy Now.
On the Confirm Order page, read and agree to the terms of service and click Pay to complete the payment.
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.