Release Notes
Product Announcements
Enabling or Disabling Serverless for a Provisioned Resource Cluster
A provisioned resource cluster supports enabling or disabling Serverless. Enabling Serverless allows the cluster to simultaneously mount both provisioned resource read-only nodes and Serverless read-only nodes. Since Serverless services are billed based on actual computation and storage resource usage, features such as automatic start/stop and auto scale-in/out are provided. As a result, enabling Serverless helps you better manage the application of each node within the provisioned resource cluster while optimizing cost control. This document provides guidance on enabling or disabling Serverless for a provisioned resource cluster.
Prerequisites
A provisioned resource cluster has been created. For operation instructions, see Creating a Cluster.
Must-Knows
After Serverless is enabled for a provisioned resource cluster, the provisioned resource read-only nodes use the parameter template of the provisioned resource cluster and support parameter formulas. In contrast, the Serverless read-only nodes use the Serverless parameter template, which does not support parameter formulas.
After Serverless is enabled for a provisioned resource cluster, if the parameter being modified for a Serverless read-only node is not supported by provisioned resource nodes (including both read-write and read-only nodes), the parameter for provisioned resource nodes cannot be modified at the same time.
After Serverless is enabled for a provisioned resource cluster, if the parameter being modified for a provisioned resource node (including both read-write and read-only nodes) is not supported by Serverless read-only nodes, the parameter for Serverless read-only nodes cannot be modified at the same time.
Directions
Enabling Serverless for a Provisioned Resource Cluster
1. Log in to the TDSQL-C for MySQL console.
2. In the cluster list on the left, click the target cluster to enter the cluster management page.
3. Click Serverless Configuration in the upper-right corner.
4. In the pop-up, turn on the button after Serverless enablement, complete the following configuration, and click OK.
Parameter | Description |
Read-Only Node Computing Power Configuration | Count: Select the number of Serverless read-only nodes. The valid range is from 1 to 15, and the total number of provisioned resource read-only nodes plus Serverless read-only nodes should not exceed 15. Computing power range: Configure the computing power range for read-only nodes. Individual node configuration is not supported. |
Auto-Pause | If auto-pause is checked, you should set an auto-pause duration, which is 1 hour by default. When there are no active connections or CPU usage within this period, a database will automatically pause. After pausing, computing resources will not be billed, while storage will continue to be billed based on actual usage. If auto-pause is not checked, a database will remain running continuously. When there are no active connections or CPU usage, billing will be based on the minimum CCU computing power you have configured. Note: If the database proxy is enabled for the cluster, auto-pause cannot be configured. |
Modifying Serverless Configuration
After Serverless is enabled for a provisioned resource cluster, you can modify the configuration of Serverless read-only nodes as needed. On the cluster management page, click Serverless Configuration in the upper-right corner, and then adjust the number of Serverless read-only nodes and computing power configuration in the pop-up window.
Disabling Serverless
Note:
Disabling Serverless will immediately terminate all Serverless read-only nodes in the cluster. Operate with caution.
Terminated Serverless read-only nodes are moved to the recycle bin. If Serverless is re-enabled for the corresponding cluster during the retention period, the Serverless read-only nodes to be mounted will be restored from the recycle bin first. If the number of nodes to be restored is less than the number of Serverless read-only nodes in the recycle bin, restoration will occur randomly. If the number of nodes to be restored exceeds the number of Serverless read-only nodes in the recycle bin and the system determines that the total number of read-only nodes in the cluster remains below 15 after restoration, all Serverless read-only nodes in the recycle bin will be restored first.
After disabling Serverless, you can add new provisioned resource read-only nodes as long as the total number of Serverless read-only nodes in the recycle bin and provisioned resource read-only nodes in the cluster remains below 15. If the total number exceeds 15, additional provisioned resource read-only nodes cannot be added. In that case, you should first remove Serverless read-only nodes from the recycle bin before proceeding.
1. Log in to the TDSQL-C for MySQL console.
2. In the cluster list on the left, click the target cluster to enter the cluster management page.
3. Click Serverless Configuration in the upper-right corner.
4. In the pop-up, turn off the button after Serverless enablement, click OK to disable Serverless and destroy the instance.
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