The Hologres console supports self-service instance upgrades, enabling you to quickly manage and perform upgrade tasks. This topic describes how to upgrade a Hologres instance.
Self-service upgrade
Limits
-
To perform a self-service upgrade, a Resource Access Management (RAM) user must have the AliyunHologresFullAccess permission. For more information about RAM user permissions, see Grant permissions to a RAM user.
-
The upgrade methods vary based on the instance version:
Major version
Minor version
Hot upgrade
Description
V1.1
Not supported
The default is a standard upgrade. You can upgrade to V1.3.62 or later.
V1.3
<V1.3.62
Not supported
The default is a standard upgrade. You can upgrade to V1.3.62 or later.
>=V1.3.62
Supported
The default is a hot upgrade.
V2.0
<V2.0.46
Not supported
The default is a standard upgrade.
>=V2.0.46
Supported
The default is a hot upgrade.
V2.1
<V2.1.11
Not supported
The default is a standard upgrade.
>=V2.1.11
Supported
The default is a hot upgrade.
Versions later than V2.1
Supported
The default is a hot upgrade.
NoteYou can upgrade across only one major version at a time. Upgrades across two or more major versions are not supported.
Procedure
-
Log on to the Hologres console. In the left navigation pane, click Instances.
-
On the Instances page, click the name of the target instance.
-
On the Instance Details page, click Upgrade Version next to the Version parameter.
-
In the Upgrade Version panel, select an Upgrade Version and click Prepare Upgrade.
Upgrade Version: Select the most stable major version and the most stable minor version for your current version based on your business needs. For more information, see Version guide.
ImportantThe upgrade preparation step runs a pre-check on the instance. This check includes query compatibility and performance for the instance version. Note:
-
Instance impact: The instance is not affected during the upgrade preparation.
-
Preparation duration: The upgrade preparation typically takes 1 to 3 hours. The actual time varies based on the instance specifications and data volume. Please wait for the process to complete.
-
Preparation status descriptions:
-
Pending Upgrade: The upgrade preparation is complete. The version check found no compatibility or performance issues. You can proceed with the upgrade. You must complete the upgrade within 7 days. If the time limit is exceeded, you must run the upgrade preparation again.
-
Preparation Failed: The check found exceptions. There may be issues such as SQL incompatibility or performance degradation. You can submit a ticket to report the issue and follow the steps suggested by the O&M engineer.
-
-
-
After the upgrade preparation is successfully completed, in the Upgrade Version panel, select an Upgrade Time and click Upgrade Now.
Upgrade time description:
-
Start Now: The upgrade process starts right away.
-
Custom Time: Select a time to stop write operations on the instance. During a hot upgrade, the steps before write operations are stopped do not affect the instance. Therefore, when performing a hot upgrade, you can choose an appropriate time to stop write operations to minimize the impact on your instance.
-
-
In the dialog box that appears, click OK to start the upgrade.
Self-service upgrade operation logs
The operation records of self-service upgrades are recorded in ActionTrail. For more information about how to query operation audit information, see Event audit log.
Version guide
Hologres is backward compatible and provides major and minor versions for you to choose from for upgrades.
-
Major version: The latest and most stable major version is provided. A major version usually includes new features or optimizations for existing features. For more information, see Feature release history.
-
Minor version: A minor version usually includes bug fixes. The latest stable minor version for the current major version of your instance is provided. For example, if your instance is on major version 2.1 and Hologres provides 2.1.60 as the latest stable minor version, you can choose to upgrade to version 2.1.60.
Regularly upgrade to the latest version based on your business needs to improve instance stability.
Upgrade methods
Hologres supports two upgrade methods: standard upgrade and hot upgrade. The following describes each method.
Service unavailability during an upgrade due to differences in instance data volume is not covered by the Service-Level Agreement (SLA).
|
Upgrade method |
Upgrade Time |
Instance status |
Job status during upgrade |
Description |
|
Standard upgrade (downtime upgrade) |
5 to 10 minutes |
The service is unavailable due to downtime during the upgrade. |
|
|
|
Hot upgrade |
10 to 30 minutes |
During the upgrade, the service is in a read-only state. The query service is not affected, but the write service is unavailable. |
|
Upgrade methods for different product editions
Different product editions support different upgrade methods. You can choose an upgrade method based on your business needs:
|
Product offering |
Standard upgrade (downtime upgrade) |
Hot upgrade |
|
Standard instances, primary/secondary instances, compute group instances |
Supported |
Supported (default) Note
For primary/secondary instances, the system uses a combined upgrade method by default. The primary instance is upgraded using a standard upgrade, and the secondary instance is upgraded using a hot upgrade. During the upgrade, the secondary instance may experience a transient disconnection. This method minimizes the impact on the secondary instance. |
|
Shared cluster |
Supported (default) Note
Shared clusters are upgraded by Hologres O&M engineers at a specified time. You cannot upgrade a single instance separately. For the specific upgrade time, follow the product announcements. |
Not supported |
Common errors for upgrade preparation failure
|
Sample error message |
Solution |
|
The following databases contain tables that use the Segment format. Upgrades to V2.0 or later are not supported. Database: xxx; Number of tables in Segment format: xxx Database: xxx; Number of tables in Segment format: xxx |
Change the data storage format of column-oriented tables. After the batch conversion is complete, click Terminate Upgrade to terminate the current upgrade. Then, submit the upgrade preparation again to upgrade to the latest version. |
|
The instance has Flink jobs that access and read binary logs in HoloHub mode. Upgrades to V2.1 or later are not supported. |
Complete the related operations as described in Default behavior changes in V2.0 (June 2023) and contact technical support. Then, click Terminate Upgrade to terminate the current upgrade and submit the upgrade preparation again to upgrade to the latest version. |
|
The instance has Flink jobs that access Hologres in RPC mode. Upgrades to V2.0 or later are not supported. |
Complete the related operations as described in Default behavior changes in V2.0 (June 2023) and contact technical support. Then, click Terminate Upgrade to terminate the current upgrade and submit the upgrade preparation again to upgrade to the latest version. |
|
The service-linked role does not exist. Upgrades to V2.2 or later are not supported. |
Create a Hologres service-linked role. Then, click Terminate Upgrade to terminate the current upgrade and submit the upgrade preparation again to upgrade to the latest version. |