Version Upgrade Notes

This document outlines the precautions for upgrading versions. Please read carefully before proceeding with subsequent upgrade operations.

need migrate data, skip installation

When the installer detects that the component versions currently installed are inconsistent with those in the upgrade package, it cannot perform the upgrade through direct replacement.

Data migration via scripts is required before the upgrade can proceed.

• Using HENGSHI built-in database (metadb), refer to Database Service Upgrade
• Using HENGSHI built-in object storage (minio), refer to Object Storage Service Upgrade

Upgrade from Version <=4.2 to This Version

1. Metadb version does not support 9.x versions. Please confirm the Metadb version information before upgrading.

   1. If using the built-in database of HENGSHI, refer to Database Service Upgrade.
   2. If using an external database, upgrade the database version independently. The recommended version is 13.xx.

2. JDK version no longer supports version 1.8. This issue can be ignored for container and K8s deployment methods. For VM standalone or cluster deployment methods, it is necessary to execute init-os all before performing the upgrade operation.

   1. For internal network environments, contact after-sales personnel to obtain JDK static resources.

cd /opt/hengshi/lib
export hs_version="openjdk-11.0.17_8.1"
wget https://download.hengshi.com/hs-jdk/${hs_version}.tar.gz
tar -zxf ${hs_version}.tar.gz && rm ${hs_version}.tar.gz
ln -sf ${hs_version} jdk

2. Note: If there is a requirement to use a specific JDK version, configure the following parameters in conf/hengshi-sense-env.sh:

export HS_JDK_HOME="JDK installation directory"  # Location of the parent directory above the bin directory

3. A built-in Doris engine is provided. If there is a need to use Doris engine as the default built-in engine, refer to Doris Engine Configuration.

Rollback to Version<4.4

1. Version 4.4 optimizes the Greenplum engine at the logical level, making it incompatible with programs running on Version<4.4. Before performing the rollback operation, execute the following steps:

cd /opt/hengshi
bin/clean_engine.sh -d true

After execution, proceed with the version rollback operation.

Notes on Using External PostgreSQL Database to Replace Metadb

Please refer to Replacing HENGSHI Metadb, specifically the Granting Permissions to Users Using Super Administrator Account step in the preparatory work.

Configuration Notes for Secondary Path

This version no longer supports using the CONTEXT_PATH parameter to achieve secondary path access.
If secondary path access is required, please refer to Secondary Path Configuration.

Precautions for Cleaning Minio

In previous versions, some scenarios of deleting apps did not remove images, resulting in some unused images in Minio. Therefore, unused images in Minio need to be cleaned, the deletion logic needs to be improved, and the storage layout needs to be reorganized.

Please make the following preparations before upgrading.

1. Back up Minio (including cloud environments) and metadb.
2. During the upgrade, wait for the cleaning logic to complete. You can monitor the progress of the cleaning by observing the logs and filtering relevant information using MinioImageClean. According to tests, cleaning 11GB of unused images takes approximately 4 minutes.

Note

Versions 4.5.4 and earlier, version 4.6, and version 4.6.1 will execute Minio cleaning operations when upgrading to the current version. Other versions upgrading to the current version will not execute Minio cleaning operations.

Modify Default Configuration for LDAP Authentication

The default configuration for enabling user attributes in LDAP authentication is set to false, and user attributes will no longer be synchronized during upgrades. Therefore, before upgrading, please confirm whether you need to synchronize user attributes. If synchronization is required, set this configuration to true.

Tip

Upgrade Impact Scope Versions 4.5.11 and earlier, 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, and 5.1.0 need to check this configuration item when upgrading to the current version.

Notes on Modifying the Default Name of Session Cookies

The default name for session cookies is _USER_SESSION_ID. After upgrading, users will need to log in again. If the customer's system uses the original cookie name sid in its logic, it needs to be updated to the new name _USER_SESSION_ID, or the parameter can be set as export SESSION_COOKIE_NAME=sid (original cookie name).

Tip

The upgrade impact applies to versions 4.5.15 and earlier, 5.0.0~5.0.8, and 5.1.0~5.1.4. Other versions are not affected.