Upgrading the Kernel Minor Version
Download
Focus Mode
Font Size
TencentDB for MySQL periodically releases new database kernel minor versions. Upgrading the database kernel minor version enables your database instance to receive improvements in performance, enhanced security, new feature support, compatibility enhancements, and bug fixes. This document describes how to upgrade the database kernel minor version via the console and provides related instructions.
Note:
For details on the features of each database kernel minor version, see the Kernel Version Update Log.
Scenarios
When the system releases a new database kernel minor version, or when the database kernel minor version of your current instance becomes outdated and requires an upgrade to a new release, the manual upgrade can be performed through the console.
Note:
When operations that trigger instance migration (such as specification adjustment, scaling up or down disk capacity, or database version upgrade) are performed on TencentDB for MySQL, the system will not upgrade your instance to the latest kernel minor version. If needed, you can manually perform the upgrade. When a primary instance has RO instances, the system automatically checks source-replica synchronization compatibility. During primary instance migration, a minor version newer than that of the RO instances will not be used.
Warning:
If a bug occurs in the background program or the system identifies a security vulnerability, the system will send upgrade notifications via internal messages, SMS, and other channels. TencentDB for MySQL will be upgraded during your instance's maintenance window. However, this automatic upgrade is only an auxiliary system measure and does not guarantee that all instances can be upgraded to the latest kernel minor version immediately. You can check the kernel minor version status on the instance details page and manually upgrade it promptly to avoid potential risks that may exist in historical kernel minor versions. If you fail to complete the upgrade within six months after receiving an emergency service upgrade/version upgrade notification due to your own reasons, you will be responsible for any resulting losses and consequences, such as service interruption or data loss. For details, see the TencentDB for MySQL Service Level Agreement.
Upgrade Rules
To ensure data replication consistency, if an instance to be upgraded is associated with other instances (primary instance, read-only instances), the associated instances will be upgraded to the kernel minor version together.
TencentDB for MySQL version upgrade involves data migration. The migration speed typically depends on the amount of data. Please wait patiently, as your business will not be affected during this process and normal access will be maintained.
Precautions
When the version upgrade is completed, an instance switchover will be involved (resulting in a brief disconnection lasting seconds for MySQL database connections). It is recommended that applications implement an automatic reconnection feature and schedule the switchover during the instance's maintenance window. For details, see Setting Instance Maintenance Time.
If the number of tables in a single instance exceeds 300,000, it may cause the upgrade to fail and also affect database monitoring. It is recommended to reasonably standardize and control the number of tables per single instance to no more than 300,000.
The kernel minor version cannot be downgraded after upgrade.
Operation Steps
1. Log in to the TencentDB for MySQL Console. On the instance list page, locate the target instance. Click the Instance ID or Manage in the Operation column to go to the instance details page.
2. On the instance details page, at Specification Configurations, click Upgrade.
3. In the pop-up dialog box, after selecting the relevant configurations, click Upgrade.
Delay Threshold for Data Consistency Check: (This setting appears only when primary or disaster recovery instances are upgraded.) The threshold is an integer between 1 - 10 seconds. During data consistency verification, delays may occur. A data delay threshold must be set. When the delay exceeds the set value, database consistency verification will be paused until the delay falls below the specified threshold, after which the verification task will resume. Setting this threshold too low may result in prolonged migration time.
Switch Time:
During 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.
Attention:
Database kernel minor version upgrade involves data migration, so a second-level momentary disconnection of MySQL database connections will occur upon upgrade completion. It is recommended that you choose the switch time as During maintenance time. The instance will initiate the switch within the next maintenance time after the upgrade is completed.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback