This section describes how to upgrade the RDS for MySQL minor kernel version.
Application Scenarios
When a new minor version is available, you can go to the Instance Management-Basic Info page to upgrade the version.
• Upgrading during the maintainable time period: You can upgrade the instance during the maintainable time period after setting.
• Upgrading now: You can trigger an upgrade manually. If the current instance status is not Running, you need to wait for other tasks to complete. The maximum waiting period is two hours.
Constraints and Restrictions
• The service running state is normal and the primary/standby instance latency is not more than 10 seconds.
• The instance disk capacity is no more than 85%, and each database is in the normal state (without occupying the system disk). The disk usage of a single distance is no more than 45%.
• Read-only instances cannot be upgraded separately.
• The minor version upgrading is not supported when the current database kernel version is the latest version.
Precautions
• Upgrading the minor kernel version of the database will restart the MySQL instance, potentially causing service interruptions. You are advised to perform this operation during the off-peak hours. Make sure that your application supports automatic reconnection.
• When upgrading the minor kernel version for primary/standby instances, a master-slave switching will be triggered once. If the primary/standby instances are in different AZ, the master-slave switching will be triggered twice.
• When upgrading the minor version of the primary instance, if read-only instances exist, the minor version of the read-only instances will also be synchronously upgraded. The instance will be restarted after the upgrade is completed. Please select an appropriate time for upgrading.
• After the minor kernel version is upgraded, the instance will be upgraded to the new minor kernel version and cannot be downgraded.
• Masked operation during upgrading: Basic information (modifying password, resetting account permissions, modifying ports, and setting maintainable time period), backup and restoration (manual backup and restoration are masked. Automatic backup during upgrading will fail, and no intervention is required), parameter settings, database management, account management, and availability management.
• If the current instance is one-master-and-one-slave and the replication mode is semi-synchronous replication, the replication mode will be automatically changed to asynchronous replication during the upgrading process. Once the upgrade is completed, the replication mode will revert to semi-synchronous replication.
• Backup files before the upgrade cannot be restored. It is recommended to initiate a full backup after the upgrade is completed.
Procedure
Log in to the Console.
On the Instance Management page, click the primary instance name.
On the Basic Info page, go to the Database Engine Version under the Configuration Information module and click Upgrade Kernel Minor Version.
In the pop-up box, select the upgrading method and click OK.
Upgrade now: The system will immediately upgrade your database kernel version to the latest version promptly after checking that the instance is running normally.
Upgrading during the maintainable time period: The system will upgrade your database kernel version to the current latest version within the maintainable time period you set.
When the running state of the instance changes to Upgrading, start official upgrading. When the state changes to Running, the upgrading ends. You may check the upgrading progress and results in the Task Center.