Modifying the Number of Peer Nodes
Download
Focus Mode
Font Size
TDSQL Boundless supports online adjustment of the number of peer nodes. When your business scale changes, you can add or remove peer nodes to match your actual storage capacity and computing performance requirements.
Common use cases include:
Scaling Out: When business data volume grows or read/write loads increase, you need to add peer nodes to enhance storage capacity and concurrent processing capability.
Scaling In: When business volume declines or resource utilization is low, you need to remove peer nodes to reduce costs.
Upgrading from Basic Edition to Cluster Edition: The current instance is a single-node Basic Edition and needs to be scaled out to a multi-node Cluster Edition to achieve high availability.
Prerequisites
The instance status is Running.
Use Limits
Minimum Number of Nodes:
Cluster Edition
The number of full-feature replicas is set to 3: the number of peer nodes must be greater than or equal to 3.
The number of full-feature replicas is set to 2: the number of peer nodes must be greater than or equal to 2.
Basic Edition: It can only be upgraded to a Cluster Edition with three full-feature replicas. After the upgrade, the number of nodes must be greater than or equal to 3.
Multi-AZ Constraint: In multi-AZ deployment mode, the adjusted number of peer nodes must be an integer multiple of the number of AZs (2 or 3).
Mutual Exclusivity of Configuration Changes: The number of peer nodes, the node specification (CPU/memory), and the disk capacity are mutually exclusive. Only one of these items can be adjusted at a time.
Number of Replicas Constraint: The number of peer nodes must not be less than the number of full-feature replicas.
Limitations
Upgrading from Basic Edition to Cluster Edition: When a Basic Edition (single-node) instance is scaled out to multiple nodes, it will be automatically upgraded to a three-replica Cluster Edition. This operation is irreversible. Once upgraded to the Cluster Edition, you cannot revert to the Basic Edition. Please confirm before proceeding.
Billing Changes:
After the number of nodes is adjusted for a prepaid instance, the fee is recalculated based on the new configuration. The difference resulting from the scale-in operation is refunded proportionally based on the usage duration.
After the number of nodes is adjusted for a postpaid instance, billing is calculated based on the unit price corresponding to the new configuration.
Operation Impact: During the adjustment, the instance remains readable and writable. However, it is recommended to perform the operation during off-peak business hours. Brief performance fluctuations may occur during node scaling.
Steps
1. Log in to the TDSQL Boundless console. The system provides three entry points to go to the Adjust Number of Peer Nodes page.
Method 1: On the Instance List page, locate the target instance. In the Operation column, click Adjust Configurations > Adjust Peer Node.
Note:
For a Basic Edition instance, Upgrade to Cluster Edition is displayed here. This document uses a Cluster Edition instance as an example for illustration.
Method 2: On the Instance List page, locate the target instance and click its Instance ID. On the Instance Details page, click Adjust Configurations > Adjust Number of Peer Nodes in the upper-right corner of the page.
Method 3: Go to the Instance Details page. In the Number of Nodes row within the Specs Configuration section, click Modify on the right.
2. In the Adjust Number of Peer Nodes dialog box, configure the following parameters.
Parameter | Description |
New Hybrid Node Specs | Displays the CPU and memory specifications of the current peer nodes for reference only. They cannot be modified here. To adjust the specifications, see Adjusting the Instance Configuration. |
New Hybrid Nodes | Select the number of target peer nodes. |
3. Confirm the adjusted configuration and billing information, and then click OK.
After the operation is completed, you can verify in the Specs Configuration section on the Instance Details page that the number of peer nodes has been updated to the target value. If the instance is upgraded from the Basic Edition to the Cluster Edition, Configuration Info will also be displayed as Instance Type.
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