How to Seamlessly Upgrade Transwarp Data Hub Community Edition: Step‑by‑Step Guide
This guide walks you through upgrading Transwarp Data Hub Community Edition—covering application market checks, version selection, upgrade modes, required scripts, configuration parameters, pre‑upgrade checks, execution commands, and rollback procedures—to ensure a smooth, automated upgrade with minimal downtime.
Transwarp Data Hub (TDH) Community Edition provides an easy upgrade path via the application market, supporting physical clusters, private clouds, or public clouds as installation platforms.
To upgrade an application, open the application market, view installed services, click the "Check Upgrade" button, and if an "Upgrade" button appears, the service can be upgraded. Choose the target version and click "Upgrade" (or "Upgrade Now") to start the process.
The upgrade page lets you select the upgrade version and mode. TDH offers two modes: Rolling Upgrade , which keeps services available during a slower upgrade, and Fast Upgrade , which completes quickly but incurs service downtime.
Manager upgrades are performed with scripts bundled in the TDH‑Basic‑*.tar.gz package: UpgradeManager.sh (upgrade script), CheckEnvironment.sh (environment check), and Upgrade.conf (configuration). Versions prior to 5.0.1‑final do not include these scripts and must download them from the Transwarp support forum.
Key parameters in Upgrade.conf include:
ADMIN : admin username for the management UI.
PASSWORD : admin password.
IS_UPGRADE_BASIC : whether to upgrade Manager and TOS (default true).
IS_UPGRADE_REGISTRY : whether to upgrade the Registry image (default false).
REGISTRY_DATA_DIR : path to the extracted registry directory when upgrading to the commercial version.
REGISTRY_PORT : port for the Registry service when enabled.
IS_UPGRADE_MACHINE_LEARNING : whether to upgrade Machine Learning images (default false, only true for commercial upgrades).
MACHINE_LEARNING_IMAGE : path to the extracted Machine Learning image file.
USER : username for password‑less SSH login (must be a NOPASSWD sudoer).
RSA : location of the private key for password‑less login.
Before upgrading, ensure:
Sufficient disk space for the upgrade scripts (≥20 GB, ≥50 GB for commercial upgrades).
Docker volume group has enough space (≥50 GB).
/etc/hosts and each host’s hostname are correct.
Password‑less SSH is configured and the user has NOPASSWD sudo rights.
After adjusting Upgrade.conf as needed, start the upgrade with: sh UpgradeManager.sh upgradeCluster If you are not root, run: sudo sh ManagerUpgrade.sh upgradeCluster Do not execute the script repeatedly on the same node. If the upgrade fails, check transwarp/script/upgrade.log for errors, then roll back with: sh UpgradeManager.sh revertCluster Successful execution displays "Upgrade cluster finished" or "Revert cluster finished". The process is automated, reduces operational cost, and ensures a high success rate.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
StarRing Big Data Open Lab
Focused on big data technology research, exploring the Big Data era | [email protected]
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.