Upgrading a Minor Version

Precautions

• When any new minor version is released for addressing issues and vulnerabilities from the open source community, perform a minor version upgrade for your instance.
• The upgrade will cause the DB instance to reboot and interrupt services intermittently. To limit the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your applications support automatic reconnection.
• If your RDS instance is involved in a DRS task, upgrading the minor version may cause the DRS task to fail.
  You are advised to check the retention period of RDS instance binlogs before upgrading the minor version.

  • If the binlogs are within the retention period, the DRS task will automatically restart after the minor version is upgraded.
  • If the binlogs are beyond the retention period, you need to reconfigure or recreate a DRS task.
• A minor version upgrade cannot be rolled back after the upgrade is complete. If the upgrade fails, the DB instance will be automatically rolled back to the source version.
• DDL operations on events, such as CREATE EVENT, DROP EVENT, and ALTER EVENT, are not allowed during a minor version upgrade.

Notes

• If the primary and standby instances are deployed in the same AZ, upgrading the minor version will trigger a primary/standby switchover. If they are deployed in different AZs, upgrading the minor version will trigger two switchovers.
• When you upgrade the minor version of a primary instance, the minor versions of read replicas (if any) will also be upgraded automatically. Read replicas cannot be upgraded separately.
• A minor version can be upgraded in minutes.
• For primary/standby DB instances, the standby DB instance is upgraded first and then the primary DB instance is upgraded afterwards.

Constraints

• If the replication delay between primary and standby DB instances is longer than 300 seconds, the minor version cannot be upgraded.
• Minor versions cannot be upgraded for DB instances with abnormal nodes.
• RDS for MariaDB DB instances with the event scheduler enabled do not support minor version upgrades. If you want to perform a minor version upgrade, disable the event scheduler first. For details, see Enabling or Disabling Event Scheduler.

Procedure

1. Log in to the management console.
2. Click in the upper left corner of the page and choose Databases > Relational Database Service.
3. On the Instances page, click the instance name.
4. In the DB Information area on the Basic Information page, click Upgrade Minor Version next to the DB Engine Version field.

   If the minor version of your DB instance is already the latest, there is no need to upgrade the minor version.

   Figure 1 Upgrading a minor version
   

5. In the displayed dialog box, select a scheduled time and click OK.
   • Upon submission: The system upgrades the minor version immediately after you have submitted your upgrade request.
   • In maintenance window: The system will upgrade the minor version during the maintenance window that you have configured.