Configuration Item | Description |
Instance Form | Select Pre-configured resource, which reserve resources according to fixed specifications. This option is suitable for scenarios with stable business loads and predictable performance requirements. |
Billing Mode | Supports Monthly Subscription and Pay as You Go. Monthly Subscription: suitable for businesses with stable long-term demand. Pay as You Go: suitable for scenarios where demand fluctuates significantly. |
Region | Select the region where your service needs to be deployed. It is recommended to select the same region as your CVM. The private networks of cloud products in different regions are not interconnected, and the region cannot be changed after purchase. |
Database Mode | Compatible with MySQL 8.0: compatible with the MySQL 8.0 protocol. Compatible with HBase: compatible with HBase data types and APIs. |
Instance Type | Cluster Edition: It consists of multiple nodes and provides high-performance, highly available database services as a unified cluster, making it suitable for enterprise production environments. Basic Edition: Instance data is stored as a single replica, does not provide high availability, and is only suitable for personal introductory learning and experimentation. Warning: Basic Editiondoes not provide high availability. Enterprise users should not use Basic Edition instances in production environments, as this may lead to brief database service interruptions affecting production operations. Note: Basic Edition instances can be upgraded to Cluster Edition via the console after creation; however, Cluster Edition instances cannot be downgraded to Basic Edition after creation. |
Kernel Version | Select the required kernel version. |
Deployment Mode | You can select the number of AZs to deploy. Single-AZ: All resources are located in the same AZ, providing the lowest network latency. Single-AZ deployments carry disaster recovery risks. It is recommended to consider deploying primary/secondary nodes across different AZs. Two AZs: Applications run across two AZs and can withstand failures in a single AZ. Three AZs: Resources are distributed across three AZs, enabling service continuity and reduced recovery time in the event of a single AZ failure. |
AZ | Select the AZ for instance deployment. Cloud products in different AZs under the same VPC can communicate via the private network. For example, a CVM in Guangzhou Zone 2 under the same VPC can access TDSQL Boundless in Guangzhou Zone 3 via the private network. |
Number of Fully Functional Replicas | Select the number of full-featured replicas that store full data and transaction logs and can be switched to Leader at any time to provide external read/write services. TDSQL Boundless ensures strong data consistency through the Raft majority protocol. You can flexibly select the number of full-featured replicas based on your business availability requirements and cost budget. 2 replicas: provides a balanced solution between cost and disaster recovery. An instance deploys two full-featured data replicas, and the system additionally deploys one log replica in an arbitration AZ. If any full-featured replica fails, the system can automatically complete a majority election based on the remaining full-featured replica and the log replica, ensuring continuous instance availability. This solution is suitable for cost-sensitive services, internal systems, general production workloads, and scenarios that have a clear requirement for cost reduction but still need cross-AZ disaster recovery capabilities. Note: A log replica is a lightweight replica that only stores transaction logs and participates in Raft voting. It does not host user data or provide read/write services. Its sole purpose is to achieve a majority in scenarios such as dual-AZ deployments to ensure cross-AZ high availability. No additional fee is charged for log replicas. 3 replicas: provides a financial-grade high availability solution. An instance deploys three full-featured data replicas, all of which store complete data and participate in majority voting. If any full-featured replica fails, the remaining two replicas can automatically complete a majority election, enabling seamless service failover. Even in extreme scenarios with multiple replica exceptions, higher data recoverability is maintained. This solution is suitable for core business scenarios, financial-grade cross-AZ disaster recovery, or businesses with high availability requirements and sufficient budgets. |
Configuration Item | Description |
Node Type | By default, it is the Enhanced type, which is equipped with a new-generation CPU core, delivers robust computing performance and ample computing resources, possesses exceptional data read/write capabilities, and is specifically designed for large-scale website applications, high-concurrency services, and other performance-sensitive workloads. |
Node Disk Type | Enhanced SSD: A CBS is a highly available, reliable, low-cost, and customizable block storage device. It provides block-level data storage, employs a distributed three-replica mechanism, and ensures data reliability for the TDSQL Boundless distributed database. For details, see Enhanced SSD CBS Performance Specifications. Local SSD: A local disk is an NVMe SSD that delivers powerful I/O performance, with IOPS up to 240,000 (the actual IOPS rate depends on configuration, page size, and workload; this value is obtained from tests using the default MySQL 16KB page size and is for reference only). It resides on the same node as the database engine, offers extremely low I/O latency, and provides optimal performance for OLTP workloads. |
Node Disk Capacity | Select the required storage space for each node. Note: To prevent an instance from becoming unrecoverable after entering read-only mode due to complete node storage exhaustion, TDSQL Boundless reserves 8% of the storage capacity on each node by default as emergency protection space. This reserved space is not counted toward the user-available space. It is used only after the instance triggers read-only protection to support emergency recovery operations such as scaling out and data cleanup, ensuring the instance always retains the ability to be restored to a read-write state. Warning: To ensure the stable operation of database instances, TDSQL Boundless provides a storage space protection mechanism. When node storage utilization reaches a specified threshold, the system automatically enables read-only protection to prevent instance exceptions caused by storage exhaustion. To avoid instance read-only lock due to not promptly monitoring disk (storage space) changes, please set up disk utilization metric alarms. For the operation, see Setting Alarm Policies. Triggering the Read-Only Protection Mechanism: A node automatically enters read-only mode when its storage space utilization exceeds the threshold set by the tdstore_enter_readonly_threshold parameter (default value: 99%).Impact of Read-Only Protection Mode: Write operations (such as INSERT and UPDATE) are rejected, but data query and cleanup operations (such as DROP and TRUNCATE) are unaffected. Data read/write operations on other nodes that have not triggered the threshold are also unaffected. Note: In a 3-replica scenario, if two or more replicas enter read-only mode, the entire instance will enter read-only mode. Automatic Recovery from Read-Only Mode: The node automatically reverts to read-write mode when you reduce its space utilization below the threshold set by the tdstore_leave_readonly_threshold parameter (default value: 95%) through actions such as scaling out or cleaning up data.Threshold Calculation Example: Take a single node with a total capacity of 500 GB as an example. Triggering Read-Only Protection: Read-only mode is triggered when user data reaches 500 GB × (99% − 8%) (system reserved) = 455 GB. Automatic Recovery to Read-Write Mode: The node automatically reverts to read-write mode when user data decreases to 500 GB × (95% − 8%) = 435 GB. |
Number of Nodes | Select the required number of peer nodes. |
Configuration Item | Description |
Network | Supports VPC environments. You can select the network and subnet for the instance. If the existing network is unsuitable, you can create a VPC or create a subnet. Note: Subnet is a logical network space within a VPC. You can create subnets in different AZs under the same VPC. Subnets in different AZs under the same VPC can interconnect via the private network by default. After the network is selected, the subnet IP address defaults to that of the same AZ as the selected instance. You may also manually choose subnet IP addresses within other AZs in the same region. Business connections follow proximity-based routing logic without adding network latency. It is recommended to choose the same VPC as your CVM in the same region; otherwise, the CVM and database will be unable to connect via the private network. The default setting is Default-VPC (default). |
Custom Port | The access port for the database. The default port is 3306. Valid range: 1024 - 65535. |
Tag | Adds Tags to the instance for categorizing and managing instance resources. |
Configuration Item | Description |
Instance Name | Name It Later: Set the instance name after the instance is created. Name It Now: Set the instance name directly during creation. |
Parameter templates | Select the required parameter template from the drop-down list. This applies only to instances with a kernel version ≥ 21.6.x. Default: Suitable for general business scenarios. Write Optimized: Suitable for write-intensive business scenarios. Read Optimized: Suitable for read-intensive business scenarios. |
Character Set | Applies only to MySQL compatibility mode. The default value is UTF8MB4. Supports UTF8, LATIN1, GBK, UTF8MB4, and GB18030. |
Table Name Case Sensitivity | Applies only to MySQL compatibility mode. Specifies whether table names are case-sensitive. In MySQL compatibility mode, the case sensitivity setting for table names cannot be changed after it is specified. Please configure with caution. |
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