The Hologres console supports manual instance version upgrades, allowing you to quickly manage and execute instance upgrade tasks. This topic describes how to upgrade Hologres instances.
Manual upgrade
Limits
Only Hologres V1.1 and later are supported.
Hologres versions earlier than V1.3.10 use regular upgrades by default and do not support hot upgrades. Hologres V1.3.10 and later use hot upgrades by default.
When RAM users perform manual upgrades, they must be attached the AliyunHologresFullAccess policy. For more information about RAM user permissions, see Grant permissions to a RAM user.
Procedure
Log on to the Hologres console, and click Instances in the left-side navigation pane.
On the Instances page, click the name of the target instance.
On the Instance Details page, click Version for upgrade next to the Version parameter.
In the Upgrading an instance panel, select a version for Version for upgrade, and then click Start upgrade preparation.
Version for upgrade: You can select the most stable major version and the most stable minor version of the current major version based on your business requirements. For more information, see Version description.
ImportantUpgrade preparation provides pre-upgrade checks for the instance, including query compatibility and performance checks.
Instance impact: The upgrade preparation does not affect the use of the instance.
Preparation duration: Upgrade preparation generally takes 1 to 3 hours, depending on the instance specifications and data volume.
Preparation status description:
Pending Upgrade: The upgrade preparation is complete, and the version check shows no compatibility or performance issues. You can proceed with the upgrade. The upgrade must be completed within 7 days. Otherwise, you need to perform the upgrade preparation again.
Preparation Failed: The check results show exceptions, which may include SQL compatibility or performance regression issues. You can submit a ticket to report the issues and follow the recommendations from the operations team for subsequent steps.
After the upgrade preparation is successfully completed, in the Upgrading an instance panel, configure Upgrade Time, and then click Upgrade now.
Upgrade time description:
Start Now: Start the upgrade process immediately, following the upgrade steps.
Custom Time: Select the time when the instance stops writing. During the hot upgrade process, the steps before the instance stops writing have no impact on the instance. Therefore, when performing a hot upgrade, you can reasonably select the time when the instance stops writing to minimize the impact on the instance.
In the dialog box that appears, click OK to start the upgrade.
Operation logs of manual upgrades
The operation records of manual upgrades are recorded in ActionTrail. For information about how to query ActionTrail information, see Event audit logs.
Version description
Hologres has backward compatibility capabilities and provides major and minor versions for upgrades.
Major version: Provides the latest and most stable major version. Major versions typically include new features and optimizations of existing features. For more information, see Release notes.
Minor version: Provides the latest and most stable minor version corresponding to the major version of the current instance. Minor versions generally include bug fixes. For example, if the current major version of the instance is V2.1 and the latest and most stable minor version is V2.1.60, you can choose to upgrade the instance to V2.1.60.
We recommend that you regularly upgrade to the latest version based on your business requirements to improve instance stability.
Upgrade modes
Hologres supports two upgrade modes: regular upgrade and hot upgrade. The following table provides details about these two upgrade modes.
The upgrade duration varies based on the amount of data that is stored in a Hologres instance. Service interruption caused by instance upgrades is not specified in the service level agreement (SLA).
Upgrade mode | Upgrade duration | Instance status | Job status during upgrade | Description |
Regular upgrade (service interruption) | 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 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 based on your business requirements.
Product form | Regular upgrade (service interruption) | Hot upgrade |
Standard instance, primary/secondary instance, virtual warehouse instance | Supported | Supported (default) Note For primary/secondary instances, the backend uses a packaged upgrade approach by default, where the primary instance uses a regular upgrade and the secondary instances use a hot upgrade. During the upgrade process, the secondary instances will experience a transient disconnection. This approach minimizes the impact on the secondary instances. |
Hologres Shared Cluster instance | Supported (default) Note Hologres Shared Cluster instances are upgraded by Hologres operations personnel at a specified point in time. Individual instances cannot be upgraded separately. Please follow the product announcements for specific upgrade time. | Not supported |
Common upgrade preparation failure errors
Sample error message | Solution |
The following databases contain tables using 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 completing the batch conversion, click Terminate upgrade to terminate the current upgrade, and submit a new upgrade preparation request to upgrade to the latest version. |
A Flink deployment to access binary logs in HoloHub mode exists in the instance. You cannot upgrade the instance to V2.1 or later. | Refer to Default behavior changes in Hologres V2.0 released in June 2023 to complete the related operations and contact technical support. Then, click Terminate upgrade to terminate the current upgrade, and submit a new upgrade preparation request to upgrade to the latest version. |
A Flink deployment to access Hologres in remote procedure call (RPC) mode exists in the instance. You cannot upgrade the instance to V2.0 or later. | Refer to Default behavior changes in Hologres V2.0 released in June 2023 to complete the related operations and contact technical support. Then, click Terminate upgrade to terminate the current upgrade, and submit a new upgrade preparation request to upgrade to the latest version. |
The service-linked role does not exist. You cannot upgrade the instance to V2.2 or later. | Create a Hologres service-linked role. Then, click Terminate upgrade to terminate the current upgrade, and submit a new upgrade preparation request to upgrade to the latest version. |