tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Upgrading Kernel Minor Version of Database Proxy

PDF
Focus Mode
Font Size
Last updated: 2026-01-29 17:54:30
TDSQL-C for MySQL irregularly updates the database proxy version. New versions may involve feature updates, performance optimization, or issue fixes. You can view the database proxy version update notes and assess the need for an upgrade based on the actual business situation. This document introduces the operations and instructions for manually upgrading the database proxy version through the console.

Prerequisites

The database proxy version of the current instance is not the latest version.

Upgrade Solutions

You can select the upgrade switch time according to the actual business situation to achieve a smoother upgrade.
Within maintenance time: An upgrade can be performed within the instance maintenance time. To set the instance maintenance time, see Modifying Instance Maintenance Time.
Upon upgrade completion: The selected database proxy version can be immediately switched to upon completion of the upgrade.
Rolling upgrade: New database proxy version nodes can be started. After startup, new connections will access the database through new database proxy version nodes, and old database proxy version nodes will no longer accept new connection requests. The switch waiting time can be set. When the switch time is reached, old database proxy version nodes will be reclaimed, and existing old connections on old nodes will be disconnected.

Must-Knows

During the database proxy version upgrade process, there will be a second-level momentary disconnection. Perform the upgrade during off-peak hours if possible, and ensure your application has an automatic reconnection mechanism.
When the database proxy version is upgraded, all proxy nodes will be upgraded simultaneously by default. If some proxy nodes have status exceptions, the upgrade cannot proceed.
The database proxy version can be upgraded only and cannot be downgraded.

Executable Tasks During Upgrade

During the database proxy version upgrade process, when Status/Task is Upgrading kernel minor version, you can perform the following operations on the database proxy: Modify the database proxy network, modify the private network address of the database proxy, and modify the remarks of the database proxy address. You cannot perform the following operations on the database proxy: Adjust configuration, disable the database proxy, upgrade the kernel minor version, rebalance the load, modify the network, or modify the IP address. To perform these operations, complete the upgrade task immediately.


Upgrading the Database Proxy Version

1. Log in to the TDSQL-C for MySQL console, select the region at the top, and click the target cluster ID to go to the Cluster Management page.
2. On the Cluster Management page, select the Database Proxy page.
3. On the Database Proxy page, choose Overview > Basic Info > Proxy Version, and click Upgrade Kernel Minor Version.

4. In the pop-up dialog box, select the target version of the upgrade, and select the upgrade switch time. After confirming that everything is correct, click OK.

Parameter
Operation Instruction
Current Version
The current database proxy version of the instance is displayed.
Target Version
Select the target database proxy version. For update notes of each version, see Database Proxy Version Update Notes.
Switch Time
Select the upgrade switch time. Available options: Within maintenance time, Upon upgrade completion, and Rolling upgrade.
During maintenance time: If you select Within maintenance time, the upgrade switch will be completed during the next maintenance period.
Upon upgrade completion: If you select Upon upgrade completion, the switch will be performed immediately when the version upgrade is completed.
Rolling upgrade: If you select Rolling upgrade, you need to set the switch waiting time (default time: 10 seconds; value range: 10 to 3600 seconds). When the switch waiting time is reached, the system will reclaim the old version nodes.
Nodes to Upgrade
The database proxy node information involved in this upgrade is displayed under this item.

Canceling Execution

During the database proxy version upgrade process, if the switch time is set to Rolling upgrade but the switch waiting time has not been reached, you can cancel the task execution depending on the actual situation. After cancellation, the database proxy version will not be upgraded this time.
1. On the Database Proxy page, choose Overview > Basic Info > Status/Task, and click Cancel Execution.

2. In the pop-up window, click OK.

Executing Immediately

Note:
After immediate execution, the old database proxy version nodes will be immediately reclaimed, and existing connections on the old database proxy version nodes will be immediately disconnected.
During the database proxy version upgrade process, if the switch time is set to During maintenance time but the maintenance time has not been reached, or if the switch time is set to Rolling upgrade but the switch waiting time has not been reached, you can perform the upgrade immediately and switch the database proxy version by following the steps below.
1. On the Database Proxy page, choose Overview > Basic Info > Status/Task, and click Execute Now.
2. In the pop-up window, click OK.

Related APIs

API
Description
This API (UpgradeCDBProxyVersion) is used to upgrade the database proxy version.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback