Version Upgrade Considerations

This article introduces the precautions in the upgrade version. Please read carefully before proceeding with the subsequent upgrade operations.

Upgrade from Version<=4.2 to this version

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

   1. For using the HENGSHI SENSE built-in database, refer to Database Service Upgrade
   2. For using an external database, upgrade the database version on your own. It is recommended to upgrade to version 13.xx.

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

   1. For intranet environments, contact the after-sales personnel to obtain the 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 a specific JDK version is required, please configure the following parameters in conf/hengshi-sense-env.sh

export HS_JDK_HOME="JDK installation directory"  # Parent directory of the bin directory

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

Rollback to Version<4.4

1. The 4.4 version has optimized the Greenplum engine at the logical level, making it incompatible with program startup and operation in Version<4.4. Before performing a rollback operation, execute the following steps:

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

After execution, proceed with the rollback operation

Considerations for Using an External PostgreSQL Database as a Replacement for Metadb

Please refer to Replace HENGSHI SENSE metadb, the Use the super administrator account to authorize users step in the preparation.

Configuration Secondary Path Considerations

This version no longer supports accessing via the CONTEXT_PATH parameter for secondary paths. For secondary path access, please refer to Secondary Access Path Configuration

Cleanup minio Notes

Previous versions had scenarios where app deletions did not remove associated images, leading to unnecessary images being generated in MinIO. Therefore, we have cleaned up unnecessary images in MinIO, improved the deletion logic, and reorganized the storage layout.

Please prepare the following before upgrading.

1. Perform minio backup (including cloud environment) and metadb backup.
2. During the upgrade, wait for the cleanup logic to complete. You can monitor the progress of the cleanup by observing the logs and filter out relevant information using MinioImageClean. After testing, it takes approximately 4 minutes to clean up 11G of unused photos.

Tip

For versions 4.5.4 and earlier, version 4.6, and version 4.6.1, when upgrading to the current version, a minio cleanup operation will be executed. For other versions upgrading to the current version, no minio cleanup operation will be executed.

Modify Default Configuration for LDAP Authentication

LDAP authentication method enables user attribute default configuration to false, and no longer synchronizes user attributes during upgrades. Therefore, before upgrading, please confirm whether you need to synchronize user attributes. If synchronization is required, please 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, 5.1.0 require checking this configuration item when upgrading to the current version.

Notes on Modifying the Default Name of Session Cookie

The default name for the session cookie is _USER_SESSION_ID, and you will need to log in again after the upgrade. If your system logic uses the original cookie name sid, it needs to be modified to the new name _USER_SESSION_ID, or set the parameter export SESSION_COOKIE_NAME=sid (original cookie name).

Tip

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