Creating Cluster
Download
Focus Mode
Font Size
This document describes how to create a cluster with provisioned resources using the TDSQL-C for MySQL console. For information on creating a Serverless cluster, see Create a Serverless Cluster.
Prerequisites
Real-name authentication is required before purchase. For details, see Real-name Authentication Guide.
Operation Steps
1. Log in to the purchase page to complete the Database Configuration, Instance Selection, and Storage settings, and then click Next.
Parameter | Description |
Instance Mode | Selecting provisioned resource. |
Instance Engine | Select a transactional cluster. TDSQL-C for MySQL supports two instance engines: transactional cluster and analysis cluster. The transactional cluster can provide HTAP capability by enabling a read-only analysis engine in conjunction with TXSQL read-write instances, while the analysis cluster only contains read-only analysis engine instances and synchronizes the configured data source data to the analysis engine via Zero-ETL capability. |
Region | Select the deployment region for your database. |
Source AZ | Select the AZ for deployment. The AZ distribution in the corresponding region is subject to the actual purchase page. |
Multi-AZ Deployment | Select whether to enable multi-AZ deployment. If you select Yes, the secondary AZ option will appear. |
Replica AZ | Disabled by default. After you enable multi-AZ deployment, you can select your secondary AZ. |
Transfer Linkage | High IO Edition by default. |
Network | Select the network for the database instance. Currently, only Virtual Private Cloud (VPC) is supported. For security and performance considerations, only devices within the selected VPC can access this database instance through the private network. For business access, use the private network. For non-business access, such as testing or auxiliary database management, you can also access the database instance via the public network. For detailed instructions and considerations, see Enable or Disable Public Network Connection. |
Database Version | MySQL 5.7 and 8.0 are supported. |
Custom Kernel Minor Version | Select the kernel minor version. The supported options are Default and Custom. Default: Selecting this option indicates that the system automatically assigns the kernel minor version. Custom: When you select Custom, you can choose a specific version under the Stable or New Feature edition. Stable Edition: A stable version that has undergone long-term validation, with an update frequency of 3 to 4 months. New Feature Edition: It carries new features and is a general kernel minor version for the production network. |
Compute Billing Mode | The yearly/monthly subscription and pay-as-you-go modes are supported. |
Instance Type | Filtering computing specifications by instance type is supported. The supported options are as follows: all instance types, general, and exclusive. |
Compute Instance (read/write) | Select the computing specification for the read-write instance. Only one read-write instance can be configured. Note: If the required instance specifications are sold out, click Do you need it?. A pop-up window will recommend instances with the same specifications in other AZs. If none of them meet your requirements, you can submit a ticket.  |
Compute Instance (read-only) | Select the computing specification for the read-only instance. Zero to 15 read-only instances can be configured. The read-only instance type in a cluster supports selecting provisioned resource instances (indicated by the letter P) and Serverless resource instances (indicated by the letter S). Serverless resource instances can automatically scale in or out based on load changes, and fees are charged based on the actual second-level computing and storage resource usage. No computing fees are charged after an instance is paused. The total number of read-only instances in a cluster = the number of provisioned resource instances + the number of Serverless instances. You can add the corresponding read-only instances as needed.  Click Add Pre-Configured Resource Instances, select the required instance specifications in the pop-up window, and then click OK. If you need provisioned resources instances with the same specifications, click the plus sign to increase the quantity. If you need provisioned resources instances with different specifications, you can click Add Pre-Configured Resource Instances again to make a selection. If you need to modify the selected instance specifications, you can click Modify to reselect the required specifications. Click Add Serverless Resource Instances to configure computing resources and set up automatic suspension. After adding, if you need to increase the number of instances, click the plus sign to do so. Then, uniformly configure the computing resource range for the selected Serverless resources instances. After the configuration is complete, you can choose whether to enable automatic pause. If you select this option, you can set the automatic pause time. This means the database will automatically enter a paused status if it is not used within the set time period, and no computing charges will be incurred during the pause. If you deselect the option, the database will keep running continuously. The automatic pause settings can also be modified in the console after the cluster is created. (Perform this step when adding a Serverless resources instance.) Select a billing mode for the Serverless resources instance. You can choose pay-as-you-go or a resource pack. If you select a resource pack, you can bind one or more (up to 10) computing resource packs that are under your current account, are within their validity period, and are in the region selected for the cluster. If no resource pack is available, you can purchase a resource pack first. After the resource pack quota is exhausted, billing continues based on the pay-as-you-go mode. |
Auto-Renewal | The device will be automatically renewed monthly upon expiration when the account balance is sufficient. Note: Note: This item needs to be set only when the computing resource billing mode of the cluster is set to yearly/monthly subscription. |
Storage Billing Mode | Pay-as-you-go billing is supported, meaning you do not need to specify storage when purchasing. TDSQL-C for MySQL charges based on the actual hourly storage usage. Yearly/monthly subscription is supported, which means you pre-purchase storage space, and the unused portion is still billed. Note: When the computing resource billing mode is set to yearly/monthly subscription, the storage resource billing mode can be set to either yearly/monthly subscription or pay-as-you-go. When the computing resource billing mode is set to pay-as-you-go, the storage resource billing mode can only be set to pay-as-you-go. For how to choose the billing mode for storage space, see How to Choose Storage Space Billing Mode. |
2. Complete the Basic Info and Advanced Configuration settings, select the Validity Period and Quantity (only the quantity needs to be selected when the computing resource billing mode is pay-as-you-go), and then click Buy Now after the cost is confirmed.
Basic Info
Parameter | Description |
Cluster Name | You can choose to name the instance after creation or immediately. Only Chinese characters, letters, digits, underscores (_), hyphens (-), and periods (.) are supported. The length should be less than 60 characters. |
Admin Username | The default name is root. |
Password | 8–64 characters, including any three of the following types: uppercase and lowercase letters, digits, and ~!@#$%^&*_-+=|\\(){}[]:;'<>,.?/. |
Default Character Set | UTF8MB4, GBK, LATIN1, and UTF8 are supported. |
Default Collation Rule | Select the default collation rule for the character set. Specific options are subject to the actual purchase page. |
Custom Port | The default port is 3306, and custom input is supported. |
Advanced Configuration
Parameter | Description |
Enable Database Proxy | Select whether to enable the database proxy. The options are yes and no. Select yes: Set the proxy specification, AZ, and number of nodes. For setting item description, see Enabling the Database Proxy. Select no: This option indicates that the database proxy is not enabled when a cluster is created. After creation, you can enable the database proxy through the console. |
Enable AI Optimizer. | The AI optimizer is used to improve SQL efficiency. Select whether to enable the AI optimizer (cluster dimension). Default value: yes. Value range: yes, no. For detailed feature introduction, see AI Optimizer Overview. |
Security Group | Manually select a security group. The security group is optional. After the instance is created, you can manually add or modify the security group on the read-write instance. |
Parameter Template | Select or create a parameter template. |
Table Name Case Sensitivity | Select whether table names are case-sensitive. The options are case-insensitive and case-sensitive. |
Project | Specify an associated project for the cluster you want to create. |
Alarm Policy | Select or create an alarm policy. |
Tag | Add tags to facilitate resource classification and management. |
Terms and Conditions | Read and check the agreement terms. |
Note:
Details such as computing fees and storage fees are displayed when you hover the mouse pointer over Configuration Fees.
Cluster Purchase Quantity
Each user can purchase up to 50 TDSQL-C for MySQL clusters in each AZ.
3. After the cluster is purchased successfully, return to the cluster list. The cluster can be used normally when the displayed status is Running.
Subsequent Operation Steps
After a TDSQL-C for MySQL cluster is created, you can connect to it using the cluster's public or private network address or a data management platform. For details, see Connecting to a Cluster.
Related APIs
API | Description |
This interface (DescribeZones) is used to query information about available regions and AZs for purchase. | |
This API (DescribeInstanceSpecs) is used to query the instance specifications available for purchase on the purchase page. | |
This API (InquirePriceCreate) is used to query the price for purchasing a new cluster. | |
This API (InquirePriceMultiSpec) is used for batch price inquiry. | |
This API (CreateClusters) is used to purchase new clusters. | |
This API (DescribeResourcesByDealName) is used to query instances associated with an order. |
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback