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

Upgrading Kernel Minor Version

PDF
Focus Mode
Font Size
Last updated: 2025-12-16 15:13:39
TencentDB for MySQL will progressively release new minor versions of the database kernel. By upgrading to these newer minor versions, your database instance can benefit from enhanced performance, improved security, support for new features, better compatibility, and bug fixes. This document provides guidance on how to upgrade the minor version of your database kernel through the console, along with detailed explanations.
Note:
For details on the TencentDB for MySQL kernel minor version, see Kernel Version Release Notes.

Operational Scenarios

Upon the release of a new minor version of the database engine, or when the minor version of the database engine in your current instance becomes outdated and necessitates an upgrade to a newer version, you may manually execute the upgrade via the console.
Note:
In the event of a bug in the backend program or the detection of security vulnerabilities, the system will dispatch upgrade notifications through internal messages, text messages, and other means. TencentDB for MySQL will undergo upgrades and repairs during the maintenance window of your instance.
When operations that trigger instance migration in TencentDB for MySQL occur (such as scaling instance specifications, expanding or contracting disk capacity, database version upgrades, etc.), the system will not automatically upgrade your instance to the latest minor kernel version. Should you require, you may manually perform the upgrade. When the primary instance possesses RO instances, the system will automatically assess master-slave synchronization compatibility, ensuring that migrations of the primary instance do not employ a minor version newer than that of the RO instances.

Upgrade rules

If an instance to be upgraded is associated with other instances (e.g., source instance and read-only instances), these instances will be upgraded together to ensure data consistency.
TencentDB for MySQL upgrade involves data migration. The time it takes to migrate an instance depends on the size of the instance's data. Your business will not be affected during the upgrade and can be accessed as per usual.

Notes

Instance switch will be required after version upgrade is completed, which will cause your instance to disconnect for seconds. We recommend that you conduct the switch during the instance maintenance time. Make sure that your business has a reconnection mechanism. For more information, see Setting Instance Maintenance Window.
If the number of tables in a single instance exceeds 300000, upgrade may fail and database monitoring may be affected. Make sure that the number of tables in a single instance is below 300000.
The kernel minor version cannot be downgraded once upgraded.

Directions

1. Log in to the TencentDB for MySQL console. In the instance list, click the target Instance ID or Manage in the Operation column to enter the instance details page.
2. In the Specification Configurations section, click Upgrade.

3. In the pop-up window, set the configuration items and click Upgrade.
Delay Threshold for Data Consistency Check: This option is available only during source instance upgrade, which can be an integer between 1 and 10 seconds. There may be a delay during the data consistency check. You need to set a data delay threshold. The database consistency check will be paused when the delay exceeds the set value and will be resumed when the delay drops below the threshold. If the threshold value is too small, the migration may take longer.
Switch time:
Within maintenance time: If this option is selected, the switch will be started within the next maintenance time after the upgrade is completed. For details about how to set the maintenance time, see Setting Instance Maintenance Time.
Upon upgrade completion: If this option is selected, the kernel minor version switch will be performed immediately upon completion of the instance data migration.
Note:
As database upgrade involves data migration, a momentary disconnection from the MySQL database may occur after the upgrade is completed. We recommend that you set the switch time to During maintenance time, so that the switch will be initiated within the next maintenance time after the instance upgrade is completed.

Help and Support

Was this page helpful?

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

Feedback