This topic provides answers to some commonly asked questions about version management.
How do I upgrade the minor version of a cluster?
Note You cannot upgrade the specified version of a cluster. For more information, see Upgrade the cluster version.
- Log on to the PolarDB console.
- In the upper-left corner of the console, select the region where the cluster is deployed.
- Find the cluster and click the cluster ID.
- In the left-side navigation pane, choose .
- In the Upgrade Version section of the Minor Version Upgrade tab, you can select Upgrade PolarDB Database Proxy and Kernel, Upgrade Kernel Only, or Upgrade PolarDB Database Proxy Only. Note
- If PolarProxy or the database engine of the cluster is of the latest version, the Upgrade PolarDB Database Proxy and Kernel, Upgrade Kernel Only, and Upgrade PolarDB Database Proxy Only options are unavailable.
- If you select Upgrade PolarDB Database Proxy Only, only the features related to read/write splitting are upgraded, such as the consistency level, transaction splitting, and whether to offload reads from the primary node.
- Click Upgrade Now or Upgrade in Maintenance Window. Note If you select Upgrade in Maintenance Window, you can view the details of the task or cancel the task on the Scheduled Tasks page. For more information, see View or cancel a scheduled task.
- Click OK.
How do I view the information about version iteration?
The interval of version updates mainly depends on the development progress of new features and bug fixes.
- For more information about the features and time of kernel version updates, see the following topics of release notes:
- For more information about the features and time of the PolarProxy version updates, see PolarProxy release notes.
- For more information about compatibility of kernel versions, see Compatibility of engine versions.
What are the impacts of a minor version upgrade?
- Typically, a minor version upgrade takes less than 30 minutes. The cluster restarts the version during a minor version upgrade.
- During the upgrade process, the cluster has a transient connection for about 30 seconds.
- Some change-related features cannot be used during the upgrade process, but query-related features are not affected.
- You cannot downgrade PolarProxy or the database engine.
Note You cannot query the upgrade duration in the console. For more information, see Usage notes.
Why is an upgrade task displayed in the task list even if I do not submit the task?
To ensure that the cluster runs normally, the backend system maintains the cluster from time to time. We recommend that you select a maintenance window within the off-peak hours to minimize the impacts on the business.
- For more information, see Set the maintenance window.
- For more information about updates, see Engine versions.
Note You are notified of proactive O&M events in advance by email. After you confirm the events, batch operations are performed.
How do I change the switching time for minor version upgrades?
- We recommend that you select a maintenance window within the off-peak hours to minimize the impacts on the business. For more information, see Set maintenance time.
- After a task is created, you can view or cancel the task in the console. For more information, see View or cancel a scheduled task. Note Scheduled events cannot be canceled.
How do I upgrade the major version of the kernel or PolarProxy?
To upgrade PolarProxy from 1.x to 2.x, you must authorize the action time period and cluster ID, and submit a ticket to contact Alibaba Cloud engineers.
- For more information about the differences between PolarProxy versions, see PolarProxy release notes.
- For more information about major version upgrades, see Major version upgrades.
Why does it take a very long period to upgrade a minor version?
The minor version upgrade process involves multiple steps. The progress bar is not necessarily accurate. For more information about the impacts of minor version upgrades, see Usage notes.