Upgrading the Minor Kernel Version of a DB Instance

Scenarios

You can upgrade the minor kernel version of your DB instance to improve performance, optimize functions, and fix bugs.

Constraints

For details about the minor versions, see Kernel Version Release History.
When any new minor kernel version is released for addressing issues and vulnerabilities from the open source community, upgrade the minor kernel version of your DB instance immediately or during the maintenance window.
The upgrade will cause the DB instance to reboot and will interrupt services intermittently. To minimize the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your applications support automatic reconnection.
If a DB instance contains a large number of table partitions (more than 1 million), it may take more than 2 hours to reboot the instance.
If you want to upgrade the minor kernel version of your DB instance from 8.0.18 to 8.0.22 and there are more than 1,000 partitions, the upgrade may fail. Contact Huawei Cloud engineers to check the version compatibility before the upgrade.
If the primary node and read replicas of a DB instance are deployed in the same AZ, a minor kernel version upgrade will trigger a failover. If they are in different AZs, a minor kernel version upgrade will trigger two failovers. A failover means that the system fails over to a read replica in case the primary node is unavailable.
When you upgrade a minor kernel version of a DB instance, minor versions of read replicas (if any) will also be upgraded automatically. Minor versions of read replicas cannot be upgraded separately. A minor kernel version upgrade cannot be rolled back after the upgrade is complete.
DDL operations on events, such as CREATE EVENT, DROP EVENT, and ALTER EVENT, are not allowed during a minor kernel version upgrade.
If the replication delay between the primary node and read replicas is longer than 300 seconds, the minor kernel version cannot be upgraded.
If the kernel version is earlier than 2.0.51.240305, it will be upgraded to 2.0.51.240305 first.
To upgrade the kernel version to 2.0.54.240600 or later, ensure that rds_global_sql_log_bin is ON and binlog_expire_logs_seconds is greater than or equal to 86400. For details about parameter settings, see Modifying Parameters of a DB Instance.

Upgrading the Minor Kernel Version of a Single DB Instance

Log in to the management console.
Click in the upper left corner and select a region and project.
Click in the upper left corner of the page and choose Databases > GaussDB(for MySQL).
On the Instances page, click the instance name to go to the Basic Information page.
In the Instance Information area, click Upgrade in the Kernel Version field.

Figure 1 Upgrading the minor kernel version on the Basic Information page

Alternatively, go to the Instances page, click Upgrade in the DB Engine column.

Figure 2 Upgrading the minor kernel version on the Instances page
In the displayed dialog box, set Scheduled Time and click OK.

Figure 3 Upgrading the minor kernel version of a DB instance
- Upon submission: The system upgrades the minor kernel version immediately after your submission of the upgrade request. In the Task Center page, click Instant Tasks and view the task progress.
- In maintenance window: The system will upgrade the minor kernel version during a maintenance window you specify. After the operation is complete, on the Task Center page, click Scheduled Tasks and view the information about the upgrade task.

Upgrading Minor Kernel Versions of Multiple DB Instances At a Time

On the Instances page, select the desired DB instances and click Upgrade in the upper left corner of the list.

Figure 4 Upgrading minor kernel versions of multiple DB instances at a time

A maximum of 100 DB instances can be selected at a time.
In the displayed dialog box, confirm the information about the DB instances to be upgraded and set Scheduled Time.

Figure 5 Selecting a scheduled time
- Upon submission: The system upgrades the minor kernel version immediately after your submission of the upgrade request. In the Task Center page, click Instant Tasks and view the task progress.
- In maintenance window: The system will upgrade the minor kernel version during a maintenance window you specify. After the operation is complete, on the Task Center page, click Scheduled Tasks and view the information about the upgrade task.
Confirm the information, enter YES in the text box as prompted, and click OK.
- Wait for 2 to 5 minutes and check whether the upgrade has been started for the DB instance. If the upgrade has not been started, check whether the value of rds_global_sql_log_bin is ON and the value of binlog_expire_logs_seconds is greater than or equal to 86400. If the parameters are not correctly set, the upgrade cannot be performed.
- If the parameters are correctly set but the upgrade has not started, it may be because the value of rds_sql_log_bin_inconsistent_count is not 0. Wait until the value of rds_sql_log_bin_inconsistent_count becomes 0 before proceeding with the upgrade.