You can manually upgrade PolarDB for MySQL to the latest revision version. The version upgrades involve multiple aspects, such as performance improvement, new features, or bug fixes. You can choose to immediately upgrade versions or upgrade versions during the period in which operations and maintenance (O&M) are allowed.

Notes

  • Clusters are restarted during version upgrades. We recommend that you upgrade versions during off-peak hours if possible or make sure that your application has an automatic reconnection mechanism.
  • You cannot downgrade a version after the version is upgraded.

Procedure

  1. Log on to the PolarDB console.
  2. In the upper-left corner of the console, select the region where the cluster resides.
  3. Find the cluster, and then click the cluster ID.
  4. In the upper-right corner of the Basic Information page, click Upgrade to Latest Version.
    Note If the current revision version of the cluster is already the latest version, the Upgrade to Latest Version button does not appear.
    Upgrade a minor kernel version
  5. In the dialog box that appears, select Upgrade PolarDB Database Proxy and Kernel or Upgrade PolarDB Database Proxy Only based on your needs.
    update
    • Upgrade PolarDB Database Proxy and Kernel

      If you select Upgrade PolarDB Database Proxy and Kernel, you can also select Upgrade Now or Upgrade in Maintenance Window.

    • Upgrade PolarDB Database Proxy Only

      If you select Upgrade PolarDB Database Proxy Only, only the features related to read/write splitting are upgraded, such as the consistency level (global consistency), transaction splitting, and offload reads from the primary node.

    Notice
    • During the Upgrade PolarDB Database Proxy and Kernel process, transient connection errors occur for the primary endpoint and the cluster endpoint and last for 60s to 90s. Make sure that your application has a reconnection mechanism.
    • During the Upgrade PolarDB Database Proxy Only process, transient connection errors occur for the cluster endpoint and the custom endpoint and last for 30s. Make sure that your application has a reconnection mechanism.
  6. Click OK.