Upgrading Kernel Minor Version

Recent Pages

Upgrading Kernel Minor Version

Last updated: 2024-11-14 16:58:46

TDSQL-C for MySQL will release new database kernel minor versions successively. By upgrading the database kernel minor version, your database instance can gain performance enhancements, enhanced security, new feature support, compatibility improvements, and error fixes. This document shows you the operations and instructions for upgrading the database kernel minor version through the console.
Note:
For details on the features of each database kernel minor version, see Kernel Version Release Notes.
Overview
When the system releases a new database kernel minor version, or the current database kernel minor version of your cluster is outdated and needs to be upgraded to a new database kernel minor version, you can manually upgrade it through the console.
Note:
If a bug occurs in the background program or the system detects a security risk, the system will push upgrade notifications via the message center and SMS. TDSQL-C for MySQL will perform the system upgrade and repair at the specified time.
When operations that trigger cluster migration occur (such as cluster specification scaling, disk capacity scaling, and database version upgrade), the system will not automatically upgrade your cluster to the latest kernel minor version. If an upgrade is required, you can upgrade it manually.
Upgrade Rules
To ensure data replication consistency, the kernel minor versions of all associated instances (read-write and read-only instances) in the cluster whose database kernel minor version is to be upgraded will be upgraded together.
The database kernel minor version upgrade will involve data migration. The migration speed generally depends on the data size. Please be patient. Your business will not be affected during the period and can be accessed as usual.
Precautions
The database kernel minor version upgrade involves data migration. Upon upgrade completion, there will be a momentary data disconnection of a few seconds. It is recommended that you use the application with an automatic reconnection mechanism. It is recommended that you choose the switch time to be within the maintenance time. The cluster will initiate the switch within the next maintenance time after the upgrade is completed.
If the number of tables in a single instance exceeds one million, upgrade may fail and database monitoring may be affected. Please regulate the number of tables reasonably and control the number of tables in a single instance not to exceed one million.
The kernel minor version cannot be downgraded once upgraded.
Description of the Four-digit Minor Version Number
The database kernel minor versions of TDSQL-C for MySQL now support four-digit minor version numbers. The version number has been updated from three digits to four digits, which can avoid passive upgrades and ensure stable operation of instances during version updates. Meanwhile, within a major version (such as a three-digit major version like 3.1.15), the system can release multiple minor versions with new capabilities to help you better experience the new capabilities of the product.
The description of each digit in the four-digit minor version number is shown in the figure below.
﻿
Standard edition: It indicates the first minor version of a major version. For example, if the major version is 2.1.12, the first database kernel minor version number is 2.1.12.001.
Beta edition: It indicates the latest minor version of a major version. For example, if the major version is 2.1.12, the latest database kernel minor version is 2.1.12.003 or 2.1.12.004. The Beta edition provides various features in the grayscale testing.
Upgrading the Kernel Minor Version
1. Log in to the TDSQL-C for MySQL Console.
2. On the cluster list page, proceed based on the view mode you actually use to go to the database kernel minor version upgrade window.
Tab View
List view
1. In the cluster list on the left, click the target cluster to go to the cluster management page.
2. On the cluster management page, after the database version, click Details/Upgrade.
﻿
1. In the cluster list, find the target cluster and click the cluster ID or Manage in the Operation column to go to the cluster details page.
2. On the cluster details page, under Configuration Info > Database Version , click Details/Upgrade.
﻿
3. In the pop-up sidebar, click Upgrade Cluster Now.
4. In the pop-up window, select the switch time and the target kernel minor version to be upgraded, check "I have read and agreed to Database Version Upgrade", and click OK.
﻿
Switch Time
During maintenance time: After the upgrade is completed, the switch will be performed within the instance maintenance time. For more information on modifying the maintenance window, see Set Instance Maintenance Time.
Upon upgrade completion: The switch will be triggered immediately after the upgrade is completed.
5. If you want to know the progress of the upgrade task, you can go to the Task List for inquiries.
6. The upgrade is completed when the instance running status is updated to "Running".