TDSQL-C for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Suggestions on Usage Specifications
- Kernel Features
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Value-Added Services Billing Overview
- Database Audit
- Audit Rule Template
- Serverless Service
- Serverless Introduction
- Serverless Resource Pack
- Configuration Change
- Operation Guide
- Database Connection
- Configuring Network Address
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Kernel Features
- Managing Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Console Account
- Database Account
- Configuring Custom Password Strength
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Utilization of Columnar Storage Indexes
- Read-Only Analysis Engine
- Feature Limits and Compatibility
- Description of Functions and Operators
- Read-Only Analysis Engine Management
- Data Loading
- Executing Queries
- Exclusive Features
- Performance Optimization
- Performance White Paper
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Performing Backup
- Managing Backup
- Rollback
- Restoring Data from Logical Backups
- Restoring Data Through the Console
- Restoring Data from Snapshot Backup
- Data Migration
- Parallel Query
- Setting Parallel Query
- Database Security and Encryption
- Access and Authorization
- Security Group Management
- TencentDB Security Group Management
- Monitoring and Alarms
- Monitoring
- Alarms
- Monitoring Metric Alarm
- Practical Tutorial
- Data Rollback
- Database/Table-Level Rollback
- Rolling back Entire Cluster
- White Paper
- Security White Paper
- Performance White Paper
- Troubleshooting
- Connection Issues
- API Documentation
- Making API Requests
- Instance APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
DocumentationTDSQL-C for MySQLOperation GuideInstance Mode ManagementConverting Provisioned Resource Instances to Serverless Instances
Converting Provisioned Resource Instances to Serverless Instances
Last updated: 2025-03-21 16:50:46
Converting Provisioned Resource Instances to Serverless Instances
Last updated: 2025-03-21 16:50:46
A provisioned resource cluster supports converting its provisioned resource read-only instances/nodes into Serverless read-only nodes. This document provides guidance on how to convert provisioned resource read-only nodes into Serverless read-only nodes within a provisioned resource cluster.
Prerequisites
A provisioned resource cluster has been created. For operation instructions, see Creating a Cluster.
There is at least one read-only instance of provisioned resources under the cluster. To create a provisioned resource read-only instance, see Creating a Read-only Instance.
Must-Knows
After a provisioned resource instance is converted to a Serverless instance, 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 a provisioned resource instance is converted to a Serverless instance, 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 a provisioned resource instance is converted to a Serverless instance, 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.
Use Limits
If the read-only instance of the provisioned resources under the cluster has parallel query enabled, the instance does not support conversion to Serverless. If you need to convert to Serverless, please disable the parallel query capability before proceeding with the conversion.
If the read-only instance of the provisioned resources under the cluster has the column store index enabled, the instance does not support conversion to Serverless. If you need to convert to Serverless, please disable the column store index capability before proceeding with the conversion.
Directions
Note:
After conversion, parameter settings will be reset according to the default template (For example, the parameter value of max_connections will be changed to 80).
If there are no Serverless read-only nodes in the provisioned resource cluster, you can modify the computing power configuration when converting a provisioned resource read-only instance to a Serverless instance. However, if the cluster already has Serverless read-only nodes, computing power configuration cannot be modified when additional provisioned resource read-only instances are converted to Serverless instances.
During conversion, instances may experience a momentary disconnection. Ensure that your business has a reconnection mechanism.
After conversion, the node’s IP address, instance name, and instance ID remain unchanged.
After conversion, Serverless read-only nodes cannot be converted to provisioned resource read-only nodes.
1. Log in to the TDSQL-C for MySQL console.
2. In the cluster list on the left, click Target Cluster to enter the cluster management page.
3. Under instance information, find the read-only instance to be converted to Serverless, and click Switch to Serverless after its configuration.
4. Complete the following configuration in the pop-up window, check the reading items, and click OK.
Parameter | Description |
Compute Unit | Configure the computing power range. |
Auto-pause | If auto-pause is enabled, 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, the 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 enabled, the 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. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No