PolarDB for MySQL:Purchase a subscription cluster

Prerequisites

An Alibaba Cloud account is created and is used to log on to the Alibaba Cloud Management Console. For more information, see Register and log on to an Alibaba Cloud account.

Background information

PolarDB for MySQL clusters support the following editions: Cluster (2 to 16 Nodes) (Recommended), Multi-master Cluster (Database/Table) , X-Engine, and Single Node (Starter). For more information about each edition, see Editions.

Procedure

1. Log on to the PolarDB console.
2. In the upper-left corner of the page, click Create Cluster.
3. Set the Product Type parameter to Subscription.
4. Configure the parameters described in the following table.

   Parameter	Description
   Region	The region in which you want to create a cluster. After the cluster is created, the region cannot be changed. Note Make sure that the PolarDB cluster and the Elastic Compute Service (ECS) instance to which you want to connect are deployed in the same region. Otherwise, the PolarDB cluster and the ECS instance can communicate only over the Internet, which degrades cluster performance.
   Creation Method	The method used to create the PolarDB cluster. Create Primary Cluster: creates a PolarDB cluster. Create Secondary Cluster: creates a secondary cluster that is deployed in a global database network (GDN). For more information, see Add a secondary cluster. Migrate from RDS: creates a cluster by cloning the data of an ApsaraDB RDS instance and synchronizing incremental data from the ApsaraDB RDS instance to the PolarDB cluster. In most cases, this method is used for data migration. Before data migration, the read/write mode of the PolarDB cluster is Read Only. By default, binary logging is enabled. For more information, see Overview. RDS Engine Type: the engine type of the source ApsaraDB RDS instance. The value of this parameter is fixed to MySQL. You do not need to change this value. Source RDS Version: the version of the source ApsaraDB RDS instance. You can select 5.6 or 5.7. Source RDS Instance: the available source ApsaraDB RDS instances. Read-only instances are excluded. Note The list of available source instances excludes read-only instances. You cannot select instances for which the TDE or SSL feature is enabled, or instances whose data is not stored in the InnoDB storage engine. While data is restored from a backup file to the PolarDB cluster, the source instance is not interrupted. Clone from RDS: creates a PolarDB cluster by cloning the data of a specified ApsaraDB RDS instance. For more information, see Create a PolarDB for MySQL cluster by cloning an ApsaraDB RDS for MySQL instance. RDS Engine Type: the engine type of the source ApsaraDB RDS instance. The value of this parameter is fixed to MySQL. You do not need to change this value. Source RDS Version: the version of the source ApsaraDB RDS instance. You can select 5.6 or 5.7. Source RDS Instance: the available source ApsaraDB RDS instances. Read-only instances are excluded. Note The list of available source instances excludes read-only instances. You cannot select instances for which the TDE or SSL feature is enabled, or instances whose data is not stored in the InnoDB storage engine. While data is restored from a backup file to the PolarDB cluster, the source instance is not interrupted. Restore from Recycle: creates a cluster by restoring a backup of a deleted cluster from the recycle bin. Source Version: the version of the deleted cluster that you want to restore. Deleted Clusters: the name of the deleted cluster that you want to restore. Backup History: the backup that you want to restore.
   Primary Availability Zone	The primary zone in which the cluster is deployed. A zone is an independent geographical location in a region. All zones in a region provide the same level of service performance. You can deploy your PolarDB cluster and ECS instance in the same zone or in different zones. You need to specify only the primary zone. The system automatically selects a secondary zone.
   Network Type	The value of this parameter is fixed to VPC. You do not need to change this value.
   VPC VSwitch	Make sure that the PolarDB cluster and the ECS instance to which you want to connect are deployed in the same VPC. Otherwise, the cluster and the ECS instance cannot communicate over a VPC, which degrades cluster performance. If an existing VPC meets your network requirements, select the VPC. For example, if you have created an ECS instance and the VPC to which the ECS instance is connected meets your network requirements, select this VPC. Otherwise, use the default VPC and the default vSwitch. Default VPC: Only one VPC is specified as the default VPC in the region that you select. The CIDR block of the default VPC uses a 16-bit subnet mask. For example, the CIDR block of the default VPC can be 192.168.0.0/16. This CIDR block provides up to 65,536 private IP addresses. The default VPC does not count towards the quota of VPCs that you can create on Alibaba Cloud. Default vSwitch: Only one vSwitch is specified as the default vSwitch in the zone that you select. The CIDR block of the default vSwitch uses a 20-bit subnet mask. For example, the CIDR block of the default vSwitch can be 192.168.0.0/20. This CIDR block provides up to 4,096 private IP addresses. The default vSwitch does not count towards the quota of vSwitches that you can create in a VPC. 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.
   Compatibility	MySQL 8.0: fully compatible with MySQL 8.0. MySQL 8.0 supports parallel queries. In specific scenarios, the database performance increases by 10 times. For more information, see Parallel query. MySQL 5.7: fully compatible with MySQL 5.7. MySQL 5.6: fully compatible with MySQL 5.6.
   Edition	You can select Cluster (2 to 16 Nodes) (Recommended), Multi-master Cluster (Database/Table) , X-Engine, or Single Node (Starter). For more information, see Overview. Note You can select Single Node (Starter) only when Creation Method is set to Create Primary Cluster and Compatibility is set to MySQL 8.0, MySQL 5.7, or MySQL 5.6. You can select Multi-master Cluster (Database/Table) or X-Engine only when Creation Method is set to Create Primary Cluster or Restore from Recycle and Compatibility is set to MySQL 8.0.
   Minor Version	When Edition is set to Cluster (2 to 16 Nodes) (Recommended), you can set Minor Version to 8.0.1 (100% Compatible with MySQL 8.0.13) (Recommended) or 8.0.2 (100% Compatible with MySQL 8.0.18). For more information about the minor versions, see Engine versions. When Edition is set to Multi-master Cluster (Database/Table) , X-Engine, or Single Node (Starter), the value of the Minor Version parameter is fixed to 8.0.1 (100% Compatible with MySQL 8.0.13) (Recommended). You do not need to change this value. Note This parameter is available only when Compatibility is set to MySQL 8.0 for the PolarDB cluster.
   Specification Type	For PolarDB for MySQL clusters of the Cluster Edition, Multi-master Cluster (Database/Table) Edition , and X-Engine Edition, the General-purpose and Dedicated specification types are supported. Dedicated: Computing resources such as CPUs that are allocated to each cluster are exclusive to the cluster. This improves the stability and reliability. General-purpose: Idle computing resources such as CPUs are shared among clusters on the same host for cost-effectiveness. For more information about the specification types, see Comparison between general-purpose and dedicated compute nodes. Note This parameter is available only when Edition is set to Cluster (2 to 16 Nodes) (Recommended), Multi-master Cluster (Database/Table) , or X-Engine. When Edition is set to Single Node (Starter), this parameter is unavailable.
   Node Specification	If your cluster edition is Cluster (2 to 16 Nodes) (Recommended), Multi-master Cluster (Database/Table) , or X-Engine, you can select node specifications based on your business requirements. If your cluster edition is Single Node (Starter), the value of this parameter is fixed to 4 Core, 8 GB (Burstable Performance). You do not need to change this value. For more information about the specifications of compute nodes, see Specifications of compute nodes.
   Nodes	If your source cluster edition is Cluster (2 to 16 Nodes) (Recommended) or X-Engine, the system automatically creates a primary node and a read-only node that have the same specifications. You do not need to configure this parameter. Note If the primary node fails, the system upgrades the read-only node to a primary node and creates another read-only node. For more information about read-only nodes, see Architecture. If your source cluster edition is Multi-master Cluster (Database/Table) , the system automatically creates two primary nodes that have the same specifications. You do not need to configure this parameter. If your source cluster edition is Single Node (Starter), the system automatically creates a primary node. You do not need to configure this parameter.
   PolarProxy	PolarDB supports Standard Enterprise Edition and Dedicated Enterprise Edition database proxy types. Standard Enterprise Edition: If your cluster is General-purpose, you can select this database proxy type, which shares CPU resources with smart elastic scaling within seconds provided based on business loads. Dedicated Enterprise Edition: If your cluster is Dedicated, you can select this database proxy type, which occupies all allocated CPU resources and provides better stability. Compared with the previous free edition of PolarProxy, PolarProxy Enterprise Edition provides additional advanced features such as the multi-master architecture, compute nodes with elastic scaling within seconds, and proxy throttling protection. For more information, see Overview. Note PolarProxy Enterprise Edition is currently provided free-of-charge but may charge fees in the future.
   Enable Hot Standby Cluster	Specifies whether to enable the Hot standby cluster feature. When this feature is enabled, the primary cluster and a hot-standby cluster for the primary cluster are deployed in the specified region. The primary cluster contains compute nodes that serve as standbys for each other, and primary storage. The two clusters each have three replicas, which adds up to six replicas. This delivers higher SLA than when this feature is disabled.PolarDB When this feature is disabled, only the primary cluster is deployed. The cluster has three replicas, and the storage unit price is half of that when this feature is enabled. This delivers lower SLA than when this feature is enabled.
   Storage type	PolarDB supports the High-performance Edition and Standard Edition storage types. High-performance Edition: the storage type supported by historical versions of PolarDB. This was the default storage type for PolarDB clusters purchased before June 7, 2022. It delivers higher performance, reliability, and availability. This storage type is also called PSL5. Standard Edition: a new storage type for PolarDB. Standard Edition uses the Smart-SSD technology developed in-house by Alibaba Cloud to compress and decompress data at the SSD disk level. This storage type can minimize the storage costs of data while maintaining a high disk performance. This storage type is also called PSL4. Note PolarDB for MySQL The storage type of existing clusters cannot be changed to Standard Edition. To use Standard Edition, we recommend that you purchase a new cluster, set the storage type to Standard Edition, and then migrate data to the new cluster. For more information about the two storage types, see Comparison between PSL4 and PSL5.
   Storage Billing Method	PolarDB supports the Pay-as-you-go and Subscription billing methods for the storage of your clusters. Pay-as-you-go: The storage capacity is provided based on a serverless architecture. This way, you do not need to specify the storage capacity when you purchase clusters. The storage capacity of the clusters can be automatically scaled up as the volume of data increases. You are charged for the actual data volume. For more information, see Pay-as-you-go. Subscription: You must purchase a specific amount of storage capacity when you create the cluster. For more information, see Subscription. Note When Product Type is set to Subscription, the Storage Billing Method parameter can be set to Pay-as-you-go or Subscription. When Product Type is set to Pay-as-you-go, the Storage Billing Method parameter is unavailable, and the storage is billed on a pay-as-you-go basis.
   Storage Cost	The storage cost. You do not need to configure this parameter. You are charged for the amount of storage that is consumed by your data on an hourly basis. For more information, see Pay-as-you-go. Note You do not need to specify the storage capacity when you create a cluster. The system scales the storage capacity as the data volume increases or decreases. This parameter is available only when Storage Billing Method is set to Pay-as-you-go.
   Capacity	The amount of storage capacity that you want to purchase for your cluster. The value can range from 50 GB to 100 TB, in 5 GB increments. Note This parameter is available only when Storage Billing Method is set to Subscription.
   Time Zone	The time zone of the cluster. The default value is UTC +08:00. Note This parameter is available only when Compatibility is set to MySQL 8.0, MySQL 5.7, or MySQL 5.6 for the PolarDB cluster.
   Table Name Case Sensitivity	Specifies whether table names in the cluster are case-sensitive. The default value is Not Case-sensitive (Default). If table names in your on-premises database are case-sensitive, select Case-sensitive to simplify the process of data migration. Note This parameter is available only when Compatibility is set to MySQL 8.0, MySQL 5.7, or MySQL 5.6 for the PolarDB cluster. After the cluster is created, you cannot change the value of this parameter. Take caution when you configure this parameter.
   Release Cluster	The backup retention policy that is used when the cluster is deleted or released. The default value is Retain Last Automatic Backup (Automatic Backup before Release) (Default). Retain Last Automatic Backup (Automatic Backup before Release) (Default): The system retains the most recent backup when you release the cluster. Retain All Backups: The system retains all backups when you release the cluster. Delete All Backups (Cannot be restored): The system retains no backups when you release the cluster. Note This parameter is available only when the Compatibility parameter is set to MySQL 8.0, MySQL 5.7, or MySQL 5.6 for the PolarDB cluster. You may be charged for the retained backups. You can delete the backups to reduce costs. For more information, see Billing rules of backup storage that exceeds the free quota.
   Cluster Name	The name of the cluster. The name must meet the following requirements: It cannot start with http:// or https://. It must be 2 to 256 characters in length. It must start with a letter and can contain letters, digits, periods (.), underscores (_), and hyphens (-). If this parameter is left empty, the system automatically generates a cluster name. You can change the cluster name after the cluster is created.
   Resource Group	Select a resource group from the available resource groups. For more information, see Create a resource group. Note A resource group is a group of resources that belong to an Alibaba Cloud account. Resource groups allow you to manage these resources in a centralized manner. A resource belongs to only one resource group. For more information, see Use RAM to create and authorize resource groups.

5. Specify the Subscription Duration and Quantity parameters, and click Buy Now.
   Note You can create a maximum of 50 clusters at a time. This allows you to create multiple clusters in specific scenarios.
6. On the Confirm Order page, confirm your order information. Read and accept the terms of service, and then click Buy Now.
7. On the Purchase page, confirm the order and the payment method, and click Purchase.

   The cluster is created in 10 to 15 minutes after you complete the payment. Then, the newly created cluster is displayed on the Clusters page.

   Note

   • If nodes in your cluster are in the Creating state, the cluster is being created and unavailable. The cluster is available only when it is in the Running state.
   • Make sure that you have selected the region where the cluster is deployed. Otherwise, you cannot view the cluster.
   • We recommend that you purchase PolarDB storage plans if you want to store a large volume of data. Storage plans are more cost-effective than pay-as-you-go storage. Larger storage plans provide more storage at lower costs. For more information, see Use a client or the CLI to connect to an ApsaraDB RDS for MySQL instance. For more information, see Combination with storage plans.

What to do next

Configure an IP whitelist

Related API operations