Upgrading the Minor Version of a DB Instance

Scenarios

GaussDB(for MySQL) supports manual minor version upgrades, which can improve performance, add new functions, and fix bugs.

Precautions

• The upgrade will cause the instance to reboot and briefly interrupt services. To limit the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your applications support automatic reconnection.
• 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 the primary node and read replicas of an instance are deployed in the same AZ, a minor version upgrade will trigger a failover. If they are in different AZs, a minor 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 version of an instance, minor versions of read replicas (if any) will also be upgraded automatically. Minor versions of read replicas cannot be upgraded separately. A minor version upgrade cannot be rolled back after the upgrade is complete.
• DDL operations, such as CREATE EVENT, DROP EVENT, and ALTER EVENT, are not allowed during a minor version upgrade.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click Service List. Under Databases, click GaussDB(for MySQL).
4. On the Instances page, click the target instance to go to the Basic Information page.
5. In the DB Instance Information area, click Upgrade in the DB Engine Version field.
6. In the displayed dialog box, select a scheduled time and click OK.

   Upon submission: The system upgrades the minor version immediately after your submission of the upgrade request. After the operation is complete, in the Task Center page, click Instant Tasks and view the information about the upgrade task.