Help Center/ TaurusDB/ User Guide/ Version Upgrades/ Upgrading the Minor Version of an Instance
Updated on 2026-08-13 GMT+08:00
View PDF
Share

Upgrading the Minor Version of an Instance

Scenarios

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

When a new minor version is released on Huawei Cloud, you will see Upgrade in the DB Engine Version column on the Instances page. You can click Upgrade to go to the minor version upgrade page.

For details about the updates in each kernel version, see TaurusDB Kernel Version Release History.

Upgrade Scenarios

  • Depending on the kernel version, upgrading a minor version involves three scenarios.
    Table 1 Kernel version upgrade scenarios

    Upgrade Scenario

    Upgrade Path

    Description

    Scenario 1: kernel version < 2.0.51.240305

    Due to the large version gap, first upgrade the kernel version to 2.0.51.240305 or 2.0.51.2403** (subject to the version displayed on the console). After this upgrade is successful, perform a minor version pre-upgrade and a minor version upgrade in sequence.

    For details, see Scenario 1.

    The entire upgrade process takes about 5 minutes per node. The upgrade will trigger two primary/standby switchovers, which may interrupt workloads for about 30–90 seconds. To minimize the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your application has an automatic reconnection mechanism.

    Scenario 2: 2.0.51.240305 ≤ kernel version ≤ 2.0.51.2403**

    Perform a minor version pre-upgrade first. After the pre-upgrade is successful, click Upgrade again to perform the minor version upgrade.

    For details, see Scenario 2.
    • The entire upgrade process involves the upgrade of the data dictionary and will take a long time.
    • Before the upgrade, check the configurations of the following parameters:
      • rds_global_sql_log_bin must be set to ON.
      • The value of binlog_expire_logs_seconds must be greater than or equal to 86400.
      • default_collation_for_utf8mb4 must be set to utf8mb4_0900_ai_ci.

        For details, see Modifying Instance Parameters.

    • Minor version pre-upgrade
      • A temporary instance is created for verifying the upgrade process. A DR instance is created for version rollback. During this process, the original instance is not rebooted and workloads are not interrupted.
      • For an instance with a small amount of data, this process takes about 15 minutes. For an instance with a large amount of data, this process takes about 15 minutes plus an additional 20 minutes for every 1 TB of data. For example, this process takes at least 35 minutes for an instance with 1 TB of data.
    • Minor version upgrade
      • Your instance will be rebooted during the upgrade and workloads will be interrupted. The entire upgrade process takes 15–20 minutes, including a brief interruption of 1–2 minutes. Perform the upgrade during off-peak hours.
      • The synchronization delay between the original and DR instances is checked during the upgrade. To prevent upgrade failures caused by excessive delay, ensure that the minor version upgrade does not overlap with the pre-upgrade time.
      • During the upgrade, the original instance will be temporarily set to read-only until data synchronization between the original and DR instances is complete. In scenarios involving large transactions, the read-only duration may last longer than expected, which can cause the upgrade to fail.

    Scenario 3: kernel version ≥ 2.0.54.240600

    Clicking Upgrade will directly trigger a minor version upgrade to the latest version.

    For details, see Scenario 3.

    The entire upgrade process takes about 5 minutes per node. The upgrade will trigger two primary/standby switchovers, which may interrupt workloads for about 30–90 seconds. To minimize the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your application has an automatic reconnection mechanism.
  • Depending on the execution time, a minor kernel version upgrade can be performed in two ways.
    • Upon submission: The system upgrades the minor version upon your manual submission of the upgrade request.
    • In maintenance window: A scheduled upgrade task is generated. The system upgrades the minor version during the maintenance window you have specified. For details about how to change the maintenance window, see Changing the Maintenance Window of a DB Instance.

Constraints

Table 2 Constraints

Phase

Constraints

Before the upgrade
  • The original kernel versions of all instances selected for batch upgrades must be the same.
  • Scenario 2 (2.0.51.240305 ≤ kernel version ≤ 2.0.51.2403**): If the rds_global_sql_log_bin parameter is set to ON, you must connect to the database and run the following command to check whether binary logging has been enabled for all threads: 
    select @@session.rds_sql_log_bin_inconsistent_count;

    rds_sql_log_bin_inconsistent_count specifies the number of users whose sql_log_bin setting differs from the rds_global_sql_log_bin setting.

    • If the command output is 0, binlog has been enabled for all threads, and all statements can be recorded in binlogs.
    • If the command output is not 0, perform the following operations:
      • If you connect to the DB instance through DAS, view warnings on the Messages tab page of the executed SQL statements.
      • If you connect to the DB instance through the mysql client, run the following command to check the IDs of the threads that binlog has not been enabled for. The statements executed in the queried threads may not be recorded in binlogs. 
        show warnings;
  • If the replication latency between the primary node and read replicas is longer than 300 seconds, the minor version cannot be upgraded.
  • Scenario 1 (kernel version < 2.0.51.240305): If you want to upgrade the minor version of your 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.

During the upgrade
  • If an instance contains a large number of table partitions (more than 1 million), it may take more than 2 hours to reboot the instance.
  • If there are large transactions in your instance, switchovers during the upgrade may take longer than expected.
  • If there are large transactions in your instance, setting the instance to read-only during the upgrade in scenario 2 (2.0.51.240305 ≤ kernel version ≤ 2.0.51.2403**) will fail.
  • When you upgrade the minor version of an instance, minor versions of read replicas (if any) will also be upgraded. During the upgrade, the read replicas will reboot. To minimize the impact, perform the upgrade during off-peak hours. Minor versions of read replicas cannot be upgraded separately. Once you upgrade the minor version, the instance will be upgraded to the latest minor version. A minor 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 version upgrade.
  • If the message "Upgrade failed. Reduce the service load of the instance and click Retry" is displayed on the console, the upgrade fails due to heavy service load. Reduce the service load or retry the upgrade during off-peak hours.

After the upgrade
  • Scenario 2 (2.0.51.240305 ≤ kernel version ≤ 2.0.51.2403**): If the upgrade fails, the instance will be rolled back to a previous version and its data will be restored to a new instance named original_instance_name_copy. The original instance will become unavailable after the rollback. If the original instance is not deleted, it continues to be billed, but the new instance does not generate any fees. The new instance is only billed after the original instance is deleted.
  • Scenario 2 (2.0.51.240305 ≤ kernel version ≤ 2.0.51.2403**):
    • Data cannot be restored to a point in time when a data dictionary upgrade was in progress. By default, the system searches for the most recent available point in time instead.
    • During the period between a data dictionary upgrade and the next full backup, data of the instance cannot be restored to the original instance or an existing instance.
  • When data is restored from a backup, the versions of the source and destination instances must adhere to the following constraints:
    • If the source instance's kernel version is 2.0.54.240600 or later, the destination instance's kernel version cannot be earlier than 2.0.54.240600.
    • If the source instance's kernel version is earlier than 2.0.54.240600, the destination instance's kernel version cannot be 2.0.54.240600 or later.

Checking Version Information

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, click the instance name to go to the Basic Information page.
  4. In the Instance Information > Configuration area, check the value of Kernel Version.

Upgrading the Minor Version of a Single Instance

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, click the target instance name.
  4. In the Instance Information area, click Upgrade under Kernel Version.

    Figure 1 Upgrading the minor version on the Basic Information page

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

    Figure 2 Upgrading the minor version on the Instances page

  5. In the displayed dialog box, confirm instance information and click Next.

  6. The system will automatically perform a pre-upgrade check. After the pre-upgrade check is complete, review the details and check whether any items have failed. If all items pass, click Next. If any items fail, handle them based on the Check Result and then click Retry after the issues are resolved.

    During the pre-upgrade check, the following items are verified:

    • Upgrade permission check: verifies whether the upgrade permissions are enabled.
    • Instance version check: verifies whether the instance version meets the upgrade requirements.
    Figure 3 Pre-upgrade check

  7. On the displayed page, select an upgrade method and click OK. The instance begins upgrading to version 2.0.51.240305 or 2.0.51.2403**.

  8. After the instance is upgraded to version 2.0.51.240305 or 2.0.51.2403**, click Upgrade. In the displayed dialog box, confirm the instance information and click Next.

    Figure 4 Successfully upgraded to version 2.0.51.240305

    Figure 5 TaurusDB minor version pre-upgrade

  9. The system will automatically perform a pre-upgrade check. After the pre-upgrade check is complete, review the details and check whether any items have failed. If all items pass, click Next. If any items fail, handle them based on the Check Result and then click Retry after the issues are resolved.

    During the pre-upgrade check, the following items are verified:

    • Upgrade feature compatibility check: verifies whether the settings, such as binlog_expire_logs_seconds, meet the upgrade requirements. This item is displayed only when the check fails.
    • Upgrade permission check: verifies whether the upgrade permissions are enabled.
    • Instance version check: verifies whether the instance version meets the upgrade requirements.
    Figure 6 Pre-upgrade check (successful)
    Figure 7 Pre-upgrade check (failed)

  10. On the displayed page, select an upgrade method and click OK.

    Figure 8 Confirming the upgrade

    • Upon submission: The system upgrades the minor version immediately after you submit the upgrade request. Then, you can go to Task Center and view information about the upgrade task on the Instant Tasks tab page.
    • In maintenance window: The system upgrades the minor version during your configured maintenance window. Then, you can go to Task Center and view information about the upgrade task on the Scheduled Tasks tab page.

  11. In the displayed dialog box, click OK to start the pre-upgrade.

    Figure 9 Pre-upgrade check

  12. After the pre-upgrade is complete, the instance status becomes Pre-upgrade completed, which means no other operations are allowed. On the Basic Information page, click Upgrade under Kernel Version again.

    Figure 10 Upgrading the kernel version

  13. In the displayed dialog box, click OK. The system will automatically perform a pre-upgrade check.

    Figure 11 Minor version upgrade

  14. After confirming that all pre-upgrade check information is correct, click Next. In the displayed dialog box, select the upgrade mode and click OK.

    Figure 12 Pre-check for the minor version upgrade

    Figure 13 Minor version upgrade

  15. Confirm the pre-upgrade check information in the dialog box and click OK. The instance status becomes Upgrading minor version. Wait until the kernel version upgrade task is complete.

    Figure 14 Pre-upgrade check

  16. When the upgrade is complete, the instance status becomes Kernel version upgrade to be confirmed, which means no other operations are allowed. Go to the Basic Information page and click Apply Upgrade. The instance status changes to Upgrading kernel version. After the upgrade is complete, the instance status becomes normal.

    Figure 15 Checking the instance status

    Figure 16 Applying the upgrade

  17. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

    Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, click the target instance name.
  4. In the Instance Information area, click Upgrade under Kernel Version.

    Figure 17 Upgrading the minor version on the Basic Information page

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

    Figure 18 Upgrading the minor version on the Instances page

  5. In the displayed dialog box, confirm instance information and click Next.

    Figure 19 TaurusDB minor version pre-upgrade

  6. The system will automatically perform a pre-upgrade check. After the pre-check is complete, review the details and check whether any items have failed. If all items pass, click Next. If any items fail, handle them based on the Check Result and then click Retry after the issues are resolved.

    During the pre-check, the following items are verified:

    • Upgrade feature compatibility check: verifies whether the settings, such as binlog_expire_logs_seconds, meet the upgrade requirements. This item is displayed only when the check fails.
    • Upgrade permission check: verifies whether the upgrade permissions are enabled.
    • Instance version check: verifies whether the instance version meets the upgrade requirements.
    Figure 20 Pre-upgrade check

  7. On the displayed page, select an upgrade method and click OK.

    Figure 21 Confirming the upgrade

    • Upon submission: The system upgrades the minor version immediately after you submit the upgrade request. Then, you can go to Task Center and view information about the upgrade task on the Instant Tasks tab page.
    • In maintenance window: The system upgrades the minor version during your configured maintenance window. Then, you can go to Task Center and view information about the upgrade task on the Scheduled Tasks tab page.

  8. In the displayed dialog box, click OK to start the pre-upgrade.

    Figure 22 Pre-upgrade check

  9. After the pre-upgrade is complete, the instance status becomes Pre-upgrade completed, which means no other operations are allowed. On the Basic Information page, click Upgrade under Kernel Version again.

    Figure 23 Upgrading the kernel version

  10. In the displayed dialog box, click OK. The system will automatically perform another pre-upgrade check.

    Figure 24 Minor version upgrade

  11. After confirming that all pre-check information is correct, click Next. In the displayed dialog box, select the upgrade mode and click OK.

    Figure 25 Pre-check for the minor version upgrade

    Figure 26 Minor version upgrade

  12. Confirm the pre-upgrade check information in the dialog box and click OK. The instance status becomes Upgrading minor version. Wait until the kernel version upgrade task is complete.

    Figure 27 Pre-upgrade check

  13. When the upgrade is complete, the instance status becomes Kernel version upgrade to be confirmed, which means no other operations are allowed. Go to the Basic Information page and click Apply Upgrade. The instance status changes to Upgrading kernel version. After the upgrade is complete, the instance status becomes normal.

    Figure 28 Checking the instance status

    Figure 29 Applying the upgrade

  14. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

    Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, click the target instance name.
  4. In the Instance Information area, click Upgrade under Kernel Version.

    Figure 30 Upgrading the minor version on the Basic Information page

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

    Figure 31 Upgrading the minor version on the Instances page

  5. In the displayed dialog box, confirm instance information and click Next.

    Figure 32 TaurusDB minor version pre-upgrade

  6. The system will automatically perform a pre-upgrade check. After the pre-check is complete, review the details and check whether any items have failed. If all items pass, click Next. If any items fail, handle them based on the Check Result and then click Retry after the issues are resolved.

    During the pre-check, the following items are verified:

    • Upgrade permission check: verifies whether the upgrade permissions are enabled.
    • Instance version check: verifies whether the instance version meets the upgrade requirements.
    Figure 33 Pre-upgrade check

  7. On the displayed page, select an upgrade method and click OK.

    Figure 34 Confirming the upgrade

    • Upon submission: The system upgrades the minor version immediately after you submit the upgrade request. Then, you can go to Task Center and view information about the upgrade task on the Instant Tasks tab page.
    • In maintenance window: The system upgrades the minor version during your configured maintenance window. Then, you can go to Task Center and view information about the upgrade task on the Scheduled Tasks tab page.

  8. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

    Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

  9. View the results.

    On the Instances page, the instance status becomes Upgrading minor version. This process takes about 10 to 20 minutes. Then, go to the instance's Basic Information page and check the kernel version to verify whether the upgrade is successful.

Batch Upgrading the Minor Versions of Multiple Instances

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, select the desired DB instances and click Upgrade in the upper left corner of the list.

    Figure 35 Batch upgrade

    A maximum of 100 instances can be selected at a time.

  4. In the Upgrade dialog box, confirm information about the target instances.

    Figure 36 Confirming the instance information

  5. The system will automatically perform a pre-upgrade check. After the pre-check is complete, review the details and check whether any items have failed. If all items pass, click Next. If any items fail, handle them based on the Check Result and then click Retry after the issues are resolved.

    During the pre-check, the following items are verified:

    • Upgrade feature compatibility check: verifies whether the settings, such as binlog_expire_logs_seconds, meet the upgrade requirements. This item is displayed only when the check fails.
    • Upgrade permission check: verifies whether the upgrade permissions are enabled.
    • Instance version check: verifies whether the instance versions meet the upgrade requirements.
    Figure 37 Pre-upgrade check

  6. Confirm the information, select the upgrade method, enter YES in the text box as prompted, and click OK.

    Figure 38 Confirming the upgrade method

    • Upon submission: The system upgrades the minor version immediately after you submit the upgrade request. Then, you can go to Task Center and view information about the upgrade task on the Instant Tasks tab page.
    • In maintenance window: The system upgrades the minor version during your configured maintenance window. Then, you can go to Task Center and view information about the upgrade task on the Scheduled Tasks tab page.
    • Wait for 2 to 5 minutes and check whether the instance has started the upgrade. If the upgrade has not started, verify that the rds_global_sql_log_bin parameter is set to ON and binlog_expire_logs_seconds is greater than or equal to 86400. If the parameters are not correctly configured, the upgrade cannot proceed.
    • If the parameters are correctly configured but the instance still has not started the upgrade, the value of rds_sql_log_bin_inconsistent_count may be not 0. Wait until this value becomes 0, and then perform the upgrade.

  7. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

    Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

Follow-up Operations

Return to the instance list. In the navigation pane, choose Task Center and check the progress of the upgrade task.
  • If you have selected Upon submission for Scheduled Time:

    On the Instant Tasks page, search for Upgrading a DB instance version and check the execution progress. Instant tasks cannot be canceled.

  • If you have selected In maintenance window for Scheduled Time:

    On the Scheduled Tasks page, search for the instance ID and check the execution status of the upgrade task.

    If the task is in the To be executed state, you can click Cancel to cancel the task.

For details, see Viewing a Task.

FAQs

Why Is My Instance in the Kernel version upgrade to be confirmed State After an Upgrade?

If your instance is in such a state, there is a temporary DR instance. This temporary instance is running the version before the upgrade and is used for compatibility rollback in extreme scenarios. Check whether workloads are normal. If they are, click Apply Upgrade to release the temporary instance. Once the temporary instance is released, your instance cannot be rolled back to the original version.

When your instance is in such a state, you cannot modify parameters or promote a read replica to primary on the console.

APIs

Parent Topic: Version Upgrades