All Products
Search

This Product

    Hologres:Upgrade an instance

    Document Center

    Hologres:Upgrade an instance

    Last Updated:Jan 05, 2026

    Upgrade your Hologres instance from the Hologres console. This topic describes the available upgrade methods and the upgrade process.

    Procedure and notes

    Important notes

    • To perform a manual upgrade as a RAM user, you must have the AliyunHologresFullAccess permission. For more information, see Grant permissions to a RAM user.

    • The available upgrade methods vary by the current instance version:

      Major version

      Minor version

      Hot upgrade

      Description

      V1.1

      Not supported

      Defaults to a regular upgrade. Can be upgraded to V1.3.62 or later.

      V1.3

      < V1.3.62

      Not supported

      Defaults to a regular upgrade. Can be upgraded to V1.3.62 or later.

      >= V1.3.62

      Supported

      Defaults to a hot upgrade.

      V2.0

      < V2.0.46

      Not supported

      Defaults to a regular upgrade.

      >= V2.0.46

      Supported

      Defaults to a hot upgrade.

      V2.1

      < V2.1.11

      Not supported

      Defaults to a regular upgrade.

      >= V2.1.11

      Supported

      Defaults to a hot upgrade.

      V2.1+

      Supported

      Defaults to a hot upgrade.

      Note

      You can only upgrade to the next immediate major version.

    Procedure

    1. Log on to the Hologres console. In the left navigation menu, click Instances.

    2. Click your instance ID.

    3. On the Instance Details page, click Upgrade Version in the Version Information section.

    4. In the Upgrade Version panel, select a target version, and click Prepare Upgrade.

      Select a stable major version or minor version. For details, see Version details.

      Important

      The upgrade preparation step runs pre-upgrade checks. These include query compatibility and performance assessments. Key details:

      • Instance impact: The preparation process is non-disruptive and will not affect your running instance.

      • Duration: Preparation typically takes 1 to 3 hours, varying with instance specifications and data volume.

      • Statuses:

        • Pending Upgrade: Preparation complete, and all checks passed. You can proceed with the upgrade within 7 days. If the deadline is missed, re-run preparation.

        • Preparation Failed: Pre-upgrade checks identified issues (e.g., SQL compatibility problems, performance regressions). Submit a support ticket with details for guidance.

    5. After the preparation is complete, in the Upgrade Version panel, set Upgrade Time and click Upgrade Now.

      Options:

      • Start Now: Start the upgrade process immediately.

      • Custom Time: Select when data writes to your instance will cease for an upgrade. For a hot upgrade, all steps performed before the designated stop time will not affect the instance. Select an appropriate time to minimize upgrade disruption.

    6. In the dialog box, click OK to start the upgrade.

    Upgrade logs

    Manual upgrades are logged. To learn how to query these logs, see Event audit logs.

    Version details

    Hologres provides backward compatibility and offers both major and minor versions.

    • Major version: Major versions typically include new features and optimizations for existing features. We provide the latest and most stable major versions. For more information, see Release notes.

    • Minor version: Minor versions generally include bug fixes. We provide the latest stable minor version for your instance's current major version. For example, if your instance is on major version 2.1 and Hologres releases a new stable minor version 2.1.60, you can choose to upgrade to 2.1.60. For more information, see Notable fixes.

    We recommend regularly upgrading to the latest version to improve instance stability.

    Comparison between hot and regular upgrades

    Hologres supports two upgrade methods: regular upgrade (with service interruption) and hot upgrade (with minimal downtime). The following table compares these two methods.

    Note

    Service unavailability during an upgrade is not covered by the Service Level Agreement (SLA). The duration of the service interruption depends on factors such as the instance specifications and data volume.

    Upgrade method

    Upgrade duration

    Impact on the instance

    Impact on jobs

    Notes

    Regular upgrade

    5 to 10 minutes

    The instance is shut down during the upgrade, and the service is unavailable.

    • Flink:

      • For Ververica Runtime (VVR) versions earlier than 6.0.7 or Apache Flink versions earlier than 1.4.0, you must pause jobs that write to Hologres and restart them after the upgrade is complete to prevent data loss.

      • For other versions, you do not need to interrupt Hologres-related jobs. The system provides an automatic failover mechanism.

    • DataWorks data integration jobs do not require pausing for upgrades. A failover will be triggered, and jobs will automatically resume based on your failover settings. We recommend setting failover retry attempts to 10 or more for robust job resumption.

    • Hologres versions earlier than V1.3.10 only support regular upgrades.

    • Upgrades will not change your instance's endpoint. However, the IP address associated with that endpoint may change.

    Hot upgrade

    10 to 30 minutes

    During the upgrade, the service is read-only. Data query is not affected, but data write is unavailable.

    • Hologres V1.3.10 and later versions default to hot upgrades.

    • Upgrades will not change your instance's endpoint. However, the IP address associated with that endpoint may change.

    Upgrade methods by instance type

    Different instance types support different upgrade methods:

    Instance type

    Regular upgrade

    Hot upgrade

    Standard instances, primary-secondary instances, and virtual warehouse instances

    Supported

    Supported (Default)

    Note

    When upgrading a primary-secondary instance pair, the system defaults to a bundled upgrade strategy. The primary instance undergoes a regular upgrade, while the secondary instance undergoes a hot upgrade. The secondary instance will experience a brief disconnection. This method ensures minimal disruption.

    Shared cluster

    Supported (Default)

    Note

    Shared clusters are upgraded centrally by Hologres at a scheduled time. For specific times, see product announcements.

    Not supported

    Common upgrade preparation errors

    Sample error message

    Solution

    The following databases contain tables using the segment storage 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

    Update the data storage format of existing column-oriented tables. After the batch transform is complete, click Terminate Upgrade to stop the current upgrade. Then, submit a new upgrade preparation request to upgrade to the latest version.

    The instance has a Flink job that reads binary logs using HoloHub. You cannot upgrade the instance to V2.1 or later.

    Refer to V2.0 (June 2023) for solutions. After the operations, 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.

    Refer to V2.0 (June 2023) for solutions. After the operations, 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 to upgrade to the latest version.