TDSQL-C for MySQL supports automatic or manual kernel minor version upgrade. Upgrading adds new features, improves performance, and fixes issues.
For more information on the TDSQL-C for MySQL kernel minor version, see Kernel Version Release Notes.
Overview
Automatic upgrade:
Scenario 1: When the cluster encounters a critical bug or security vulnerabilities, the system will perform database kernel minor version upgrade during the maintenance window and send upgrade notifications through the Message Center and SMS.
Scenario 2: Upon the release of a new kernel minor version, you can set a version upgrade period (such as not upgrading within 30 days after release). Outside this period, when operations that trigger cluster migration occur (such as cluster specification scaling, disk capacity scaling, and database version upgrade), the system will upgrade your cluster to the latest kernel minor version.
Manual upgrade:
Upon the release of a new kernel minor version, you can set a version upgrade period (such as not upgrading within 30 days after release). Within this period, when operations that trigger cluster migration occur (such as cluster specification scaling, disk capacity scaling, and database version upgrade), the system will not upgrade your cluster to the latest kernel minor version. If an upgrade is required, you can manually upgrade the kernel minor version.
Upgrade Rules
To ensure database replication consistency, the kernel minor versions of all associated instances (read-write and read-only instances) in the cluster will also be upgraded.
TDSQL-C for MySQL upgrade involves data migration. The time it takes for migration depends on the data size. Your business will not be affected during the upgrade and can be accessed as per usual.
Notes
Cluster switch may be needed after version upgrade is completed (that is, the database may be disconnected for seconds). We recommend you use applications configured with auto reconnection feature and conduct the switch during the instance maintenance window.
If the number of tables in a single instance exceeds one million, upgrade may fail and database monitoring may be affected. Make sure that the number of tables in a single instance is below one million.
The kernel minor version cannot be downgraded once upgraded.
Upgrading Kernel Minor Version Immediately
On the cluster list page, proceed based on the actually used view mode:
Tab View
List view
1. Log in to the TDSQL-C for MySQL console,locate the cluster list on the left, and click the target cluster to enter the cluster management page.
2. On the cluster management page, after the database version, click Details/Upgrade.
3. In the pop-up sidebar, click Upgrade Cluster Now, then in the pop-up window, select the switch time, specific kernel minor version, and click OK.
Note:
As database upgrade involves data migration, after the upgrade is completed, a momentary disconnection from the database lasting for just seconds may occur. We recommend you select During maintenance time as the switch time, so that the switch will be initiated within the next maintenance time after the instance upgrade is completed.
1. Log in to the TDSQL-C for MySQL console and click a cluster name in the cluster list or Manage in the Operation column to enter 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 . In the pop-up window, select the switch time and specific kernel minor version, and then click OK .
Note:
As database upgrade involves data migration, after the upgrade is completed, a momentary disconnection from the database lasting for just seconds may occur. We recommend you select During maintenance time as the switch time, so that the switch will be initiated within the next maintenance time after the instance upgrade is completed.
Setting Kernel Minor Version Upgrade Deadline
Note:
After the kernel minor version upgrade deadline is set, the system will send upgrade notifications to your Message Center account 5 days before the deadline and on the deadline day.
On the cluster list page, proceed based on the actually used view mode:
Tab View
List view
1. Log in to the TDSQL-C for MySQL console, locate the cluster list on the left, and click the target cluster to enter the cluster management page.
2. On the cluster management page, click Details/Upgrade next to the database version.
3. In the pop-up sidebar, click the edit icon
after Version upgrade deadline .
4. Set the number of days after publication during which no upgrades will be performed (0 to 90 days supported), and then click
.
1. Log in to the TDSQL-C for MySQL console, locate the cluster list on the left, and click the target cluster to enter the cluster management page.
2. On the cluster details page, under Configuration Info > Database Version , click Details/Upgrade .
3. In the pop-up sidebar, click the edit icon
after Version upgrade deadline .
4. Set the number of days after publication during which no upgrades will be performed (0 to 90 days supported), and then click
Yes
No
Was this page helpful?