Release Notes
Product Announcements
Change from Pay-as-You-Go to Serverless Billing
The billing mode of TDSQL-C for MySQL can change from the pay-as-you-go mode to the Serverless mode. TDSQL-C for MySQL implements this change by converting the cluster type on the backend. After a successful conversion, the cluster's instance form will also change from pre-allocated resources to the Serverless form. After the conversion, bills and details will change, while the billing mode will remain as the pay-as-you-go mode.
Operation Scenarios
If the instance mode is a cluster of provisioned resource, and the computing billing mode is pay-as-you-go while the storage billing mode is also pay-as-you-go, it can be converted to a cluster with an instance mode of Serverless.
Must-Knows
During the change from pay-as-you-go billing to serverless billing, the database can be accessed normally but will experience a momentary interruption when the billing mode is changed. Therefore, we recommend you configure an automatic reconnection feature for your application.
The change from pay-as-you-go billing to serverless billing is irreversible.
After the original pay-as-you-go cluster is converted to a Serverless cluster, the original private network address will remain unchanged.
Use Limits
Clusters with parallel query enabled do not support conversion to Serverless. If you need to convert to Serverless, please disable the parallel query capability before proceeding with the conversion.
Clusters with column store index enabled do not support conversion to Serverless. If you need to convert to Serverless, please disable the columnstore index capability before proceeding with the conversion.
The change from the pay-as-you-go mode to the Serverless mode is supported only if the original cluster's regions and availability zones support creating clusters with the Serverless instance type.
Directions
1. Log in to the TDSQL-C for MySQL console.
2. Select a region at the top and proceed according to the actually used view mode:
Click Target Cluster in the cluster list on the left to enter the cluster management page, and click Pay-as-You-Go to Serverless.
Select the target instance in the instance list, and click More > Pay-as-You-Go to Serverless in the Operation column.
3. In the pop-up dialog box, set the relevant configuration of the database requiring change to the Serverless mode, read the rule, check the box of agreeing to it, and click OK.
Parameters | Note: |
Serverless | If there are only read-write instances in the original pay-as-you-go cluster, the Serverless Architecture can be set to the Single-Node Edition or the Cluster Edition. If there are both read-write instances and read-only instances in the original pay-as-you-go cluster, the Serverless Architecture will be set to the Cluster Edition by default. |
Read-Write Node Computing Power Configuration | It is used to configure the compute unit range for read-write nodes. For more information on compute unit configuration, see Service Compute Unit Configuration. |
Read-Only Node Computing Power Configuration | If the Serverless Architecture is the Single-Node Edition, this parameter is not required. If the Serverless Architecture is the Cluster Edition, you can configure the number of read-only nodes (1-8) and the compute unit range here. For more information on compute unit configuration, see Service Compute Unit Configuration. |
Auto-Pause | Checking this option indicates that the database will automatically enter a paused state if unused within a set time. Within a pause, computing resources will not be billed. After checking this option, you need to set the auto-pause time below. If this option is not checked, the database will remain in continuous operation. You can manually pause the database as needed and also enable the auto-pause feature in the console later. For details, see Auto Start/Stop. |
Switch Time | Execute Immediately: After you click OK, the task will be executed immediately. Within Maintenance Time: After you click OK, the conversion task will be executed within the next maintenance time. Note: During the operation, there will be second-level interruption. Please ensure your business has a reconnection mechanism. |
4. When the cluster status is updated from "Running Async Task: Switching Serverless" to "Running", the conversion is successful.
Note:
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