You can manually upgrade Hologres instances in the Hologres console. This lets you quickly manage and run instance upgrade tasks. This topic describes the procedure for upgrading a Hologres instance.
Manual upgrade
Limits
To perform a manual upgrade as a Resource Access Management (RAM) user, you must have the AliyunHologresFullAccess permission. For more information, see Grant permissions to a RAM user.
The available upgrade modes depend on the instance version:
Major version
Minor version
Hot upgrade
Description
V1.1
Not supported
A standard upgrade is performed by default. You can upgrade to V1.3.62 or later.
V1.3
Versions earlier than V1.3.62
Not supported
A standard upgrade is performed by default. You can upgrade to V1.3.62 or later.
>= V1.3.62
Supported
A hot upgrade is performed by default.
V2.0
Versions earlier than V2.0.46
Not supported
A standard upgrade is performed by default.
>= V2.0.46
Supported
A hot upgrade is performed by default.
V2.1
Versions before V2.1.11
Not supported
A standard upgrade is performed by default.
>= V2.1.11
Supported
A hot upgrade is performed by default.
V2.1 or later
Supported
A hot upgrade is performed by default.
NoteYou can upgrade an instance by only one major version at a time. You cannot skip major versions during an upgrade.
Procedure
Log on to the Hologres console. In the navigation pane on the left, click Instances.
On the Instances page, click the name of your instance.
On the Instance Details page, click Upgrade Version next to the Version parameter.
In the Upgrade Instance panel, select an Upgrade Version and click Prepare for Upgrade.
Upgrade Version: Select the most stable major and minor versions available for your current version as needed. For more information, see Version description.
ImportantThe preparation process runs pre-upgrade checks on the instance, including query compatibility and performance checks. Note the following:
Instance impact: The upgrade preparation does not affect your instance.
Preparation duration: The upgrade preparation typically takes 1 to 3 hours. The exact duration depends on the instance type and data volume.
Preparation statuses:
Pending Upgrade: The upgrade preparation is complete and the version check found no compatibility or performance issues. You can proceed with the upgrade. The upgrade must be completed within 7 days. Otherwise, you must prepare for the upgrade again.
Preparation Failed: The check found issues, such as SQL compatibility or performance regression issues. You can submit a ticket to report the issues and follow the recommendations from technical support.
After the preparation is successfully completed, in the Upgrade Instance panel, select an Upgrade Time and click Upgrade Now.
The following upgrade times are available:
Start Now: Starts the upgrade process immediately.
Custom Time: Select a time to stop data writes to the instance. For a hot upgrade, the steps performed before data writes are stopped do not affect the instance. This lets you select an appropriate time to stop data writes to minimize the impact on your business.
In the dialog box that appears, click OK to start the upgrade.
Operation logs for manual upgrades
Manual upgrade operations are recorded as events in ActionTrail. For more information about how to query these events, see Event audit logs.
Version description
Hologres is backward compatible and provides major and minor versions for upgrades.
Major version: Major versions typically include new features and optimizations of existing features. Hologres provides the latest and most stable major versions for you to upgrade to. For more information, see Release notes.
Minor version: Minor versions generally include bug fixes. Hologres provides the latest and most stable minor version that corresponds to the major version of your current instance. 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 upgrade the instance to version 2.1.60.
We recommend that you regularly upgrade your instance to the latest version to improve stability.
Upgrade modes
Hologres supports two upgrade modes: standard upgrade and hot upgrade. The differences are described as follows:
Service unavailability that occurs during an upgrade is not covered by the Service-Level Agreement (SLA).
Upgrade mode | Upgrade duration | Instance status | Job status during the upgrade | Description |
Standard upgrade (with downtime) | 5 to 10 minutes | The instance is shut down during the upgrade, and the service is unavailable. |
|
|
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 modes for different product forms
Different product forms support different upgrade modes. You can select an upgrade mode as needed:
Product form | Standard upgrade (with downtime) | Hot upgrade |
Standard instances, primary/secondary instances, and compute group instances | Supported | Supported (default) Note For primary/secondary instances, the backend uses a packaged upgrade by default. The primary instance is upgraded using a standard upgrade, and the secondary instances are upgraded using a hot upgrade. During the upgrade, the secondary instances experience a transient disconnection. This method minimizes the impact on the secondary instances. |
Shared cluster | Supported (default) Note Shared cluster instances are upgraded by Hologres O&M engineers at a specified time. Individual instances cannot be upgraded separately. For the specific upgrade time, follow the service notices. | Not supported |
Common upgrade preparation failure errors
Sample error message | Solution |
The following databases contain tables that use the Segment format. You cannot upgrade the instance to V2.0 or later. Database: xxx; Number of tables in the Segment format: xxx Database: xxx; Number of tables in the Segment format: xxx | Change the data storage format of column-oriented tables. After the batch transformation is complete, click Terminate Upgrade to stop the current upgrade. Then, submit a new upgrade preparation request. |
The instance has a Flink job that reads binary logs using HoloHub mode. You cannot upgrade the instance to V2.1 or later. | Follow the instructions in V2.0 default behavior changes (June 2023) and contact technical support. After the issue is resolved, click Terminate Upgrade to stop the current upgrade and submit a new upgrade preparation request. |
The instance has a Flink job that accesses Hologres in remote procedure call (RPC) mode. You cannot upgrade the instance to V2.0 or later. | Follow the instructions in V2.0 default behavior changes (June 2023) and contact technical support. After the issue is resolved, click Terminate Upgrade to stop the current upgrade and submit a new upgrade preparation request. |
The service-linked role does not exist. You cannot upgrade the instance to V2.2 or later. | Create a service-linked role for Hologres. Then, click Terminate Upgrade to stop the current upgrade and submit a new upgrade preparation request. |