tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary
DocumentationTencentDB for MySQLOperation GuideDatabase ProxyDatabase Proxy Kernel FeaturesUpgrading Kernel Minor Version of Database Proxy

Upgrading Kernel Minor Version of Database Proxy

PDF
Focus Mode
Font Size
Last updated: 2026-01-06 12:11:47
This document describes how to manually upgrade the kernel minor version of the database proxy in the console.

Prerequisite

You have enabled the database proxy. For more information, see Enabling Database Proxy.

Notes

There will be a momentary disconnection when you upgrade the kernel minor version of the database proxy. Therefore, upgrade the version during off-peak hours and make sure that your application has an automatic reconnection mechanism.
If the upgrade fails, the reason may be that the kernel minor version of the database is earlier than 20211031. You need to upgrade the kernel minor version of the database before upgrading the kernel version of the database proxy. For more information, see Upgrading Kernel Minor Version.
Versions 1.0, 1.1, and 1.2 of the database proxy kernel are legacy releases that are no longer maintained or updated. These versions may contain known issues and vulnerabilities, and are not recommended for production use. It is recommended to upgrade to version 1.3.1 or later.
Note：
In database proxy kernel versions 1.0 and 1.1, read-only instances with a weight of 0 will not establish connections. In versions 1.2 and later, they will establish connections. It is recommended to check the read-write separation settings after the version is upgraded. For instances that do not participate in read-write separation, disable them in the console rather than setting the weight to 0.


Definition Description of the Database Proxy Kernel Version

Preview version: the latest version of the database proxy, which typically includes new features, but may have unknown bugs. It is released primarily for users to experience the latest features.
Stable version: a tested and verified database proxy version, typically used in production environments. It offers greater reliability than the preview version but may not include the latest features.
Outdated version: older database proxy versions that are no longer maintained or updated. Outdated versions may have known issues and vulnerabilities and are not recommended for production use.

Directions

1. Log in to the TencentDB for MySQL console. Select the region at the top and click the target instance ID to enter the instance management page.
2. On the instance management page, select the Database Proxy tab.
3. In Overview > Basic Info > Proxy Version on the Database Proxy tab, click Upgrade Kernel Minor Version.

4. In the pop-up window, check the target version and select the upgrade switch time. After confirming that everything is correct, click OK. Switch Time:
During maintenance time: The upgrade will be performed during the maintenance time, which can be modified on the instance details page.
Upon upgrade completion: The upgrade will be performed immediately after the upgrade operation is confirmed.
Note:
After a version upgrade, rolling back to an earlier version is not supported.
There will be a momentary disconnection during upgrade. Therefore, make sure that your business has a reconnection mechanism.
Except for abnormal nodes, all nodes are upgraded at the same time by default during the kernel minor version upgrade.

Previous Topic: Kernel Minor Version Release NotesNext Topic: Enabling Database Proxy

Help and Support

Was this page helpful?

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

Feedback