Prerequisites
A Tencent Cloud account has been registered with identity verification completed.
Instance Purchase
Go to the TDSQL Boundless purchase page, and complete basic configuration, specification configuration, and initialization configuration according to actual needs. Basic Configuration
Engine: Select TDSQL Boundless.
Billing Mode: Yearly/monthly subscription and pay-as-you-go are supported. For stable long-term business demands, it is recommended to choose yearly/monthly subscription. For scenarios with significant instantaneous fluctuations in business volume, it is recommended to choose pay-as-you-go.
Region: Select the region where you need to deploy TDSQL Boundless. It is recommended to choose the same region as your CVM. Cloud products in different regions cannot communicate over the private network and the region cannot be changed after purchase.
Network: The instance supports the VPC environment. You can select the network and subnet to which the instance belongs. If the existing network is unsuitable, you can Create a new VPC or Create a new subnet. Note:
A subnet is a network space that is logical 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 increasing 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).
Specs Configuration
Compatibility Mode: supports MySQL Compatibility Mode and HBase Compatibility Mode.
Kernel Version: Different kernel versions provide distinct features. It is recommended to choose the latest stable version currently available.
Instance Type: TDSQL Boundless instances are divided into two types: cluster edition and basic edition:
cluster edition: Composed of multiple nodes, it provides high-performance and highly available database services in the form of a multi-replica Raft cluster, suitable for enterprise production environments.
Basic edition: Composed of a single node, it provides complete database features at a relatively low cost but does not include high availability, suitable for individual users.
Note:
After a basic edition instance is created, it can be upgraded to a cluster edition instance through the console. Once a cluster edition instance is created, it cannot be downgraded to a basic edition instance.
Deployment Mode: Number of AZs available for deployment. Single-AZ: All resources reside in the same AZ, delivering the lowest network latency; Two AZs: Applications run across two AZs to withstand single-AZ failures; Three AZs: Resources are distributed across three AZs, maintaining service availability during any single-AZ outage with reduced recovery time.
AZ: Select an availability zone for deploying services within a region.
Source AZ: After a primary AZ is set, database nodes in this AZ will have their weight increased to 99%, meaning 99% of requests will be handled by these nodes. Users may choose not to set a primary AZ, or can cancel/adjust the primary AZ configuration via the console.
Number of Fully Functional Replicas: Select the number of replicas capable of read and write operations that participate in voting for data consistency.
Performance Specifications: default to Enhanced, equipped with new-generation CPU cores, providing powerful computing performance and ample computing resources, featuring excellent data read/write capabilities, designed specifically for large-scale web applications, high-concurrency services, and other performance-sensitive businesses.
Storage Class: includes Cloud Disk and Local Disk.
Cloud Disk: offers higher availability and data durability, supports larger single-node capacity and rapid backup.
Local Disk: offers better throughput and IOPS, but has a longer recovery time compared to Cloud Disk.
Hybrid Node Disk Capacity: Select the storage space required for each node.
Note:
To ensure stable operation of the database, the system has a built-in storage space protection mechanism. It is crucial to closely monitor storage space usage. The rules of this mechanism are as follows:
Read-only mode trigger: When the storage space utilization of any node exceeds the threshold set by the tdstore_enter_readonly_threshold parameter (default: 99%), that node will automatically enter read-only mode. The node can still query data normally at this time, but only data cleanup operations (such as DROP/TRUNCATE) are allowed; other write operations (such as INSERT/UPDATE/DELETE) will be rejected. Read/write operations on other nodes that have not triggered the threshold remain unaffected. In a 3-replica scenario, if two or more replicas enter read-only mode, the entire instance will enter read-only mode.
This utilization threshold is calculated based on the data storage capacity of a single node. The system reserves 8% of space for its own operation. Therefore, from the user's perspective, when "Available Space" is not yet fully exhausted, the protection mechanism will be triggered as long as "Total Usage" reaches the threshold.
Example: Assume the total data storage capacity is 500GB, and the system reserves 8% of the space (40GB). Then:
User's actual available space: 500GB - 40GB = 460GB
Threshold for triggering read-only mode: 500GB × 99% = 495GB
At this point, the node's user data storage has used 495GB - 40GB = 455GB, and the node will automatically switch to read-only mode.
Recovery from read-only mode: When you reduce space utilization below the threshold set by the tdstore_leave_readonly_threshold parameter (default: 95%) through methods such as scaling out or data cleanup, the node will automatically revert to read-write mode.
Example: Assume the total data storage capacity is 500GB, and the system reserves 8% of the space (40GB). When user space usage drops to 500GB × 95% - 40GB = 435GB, the node will automatically recover to read-write mode.
Hybrid Nodes: Select the required number of peer nodes.
Initialization configurations
Character Set: Applicable to MySQL compatibility mode. Supports UTF8, LATIN1, GBK, UTF8MB4, and GB18030 character sets. The default character set encoding format is UTF8MB4.
Table Name Case Sensitivity: Applicable to MySQL compatibility mode. Specifies whether table names are case-sensitive. Note that in MySQL compatibility mode, the case sensitivity setting for table names cannot be changed after configuration. Please configure with caution.
Custom Port: The access port for the database, which defaults to 3306.
Others
Tag: Add tags to instances to facilitate categorized management of instance resources.
Instance Name: Can be named either after creation or immediately.
Complete Purchase
Quantity: Specify the number of instances to purchase for this configuration.
Click Buy Now to complete the purchase.