Coordinator / Deployer must be upgraded manually.
Coordinator / Deployer does not affect INSERT, APPEND, SELECT in Broker / Warehouse even if it is shut down.
However, it does not detect that the Broker / Warehouse also shuts down while it is shutting down. (Normally detected after restart)
Back up the dbs/ and conf/ directories located in $MACH_COORDINATOR_HOME.
Proceed with full package instead of lightweight package.
tar zxvf machbase-ent-new.official-LINUX-X86-64-release.tgz -C $MACHBASE_COORDINATOR_HOME
Unzip and overwrite the package to $MACH_COORDINATOR_HOME.
This has the same process as the Coordinator.
Back up the dbs/ and conf/ directories located in $MACH_DEPLOYER_HOME.
If you are running MWA or not running Collector on the Host the Deployer is installed, you can proceed with the lightweight package.
tar zxvf machbase-ent-new.official-LINUX-X86-64-release.tgz -C $MACH_DEPLOYER_HOME
Unzip and overwrite the package to $MACH_DEPLOYER_HOME.
To upgrade Broker / Warehouse, register the Package in Coordinator and proceed with the upgrade.
It is recommended to register with a lightweight package.
First, move the package to the Host where $MACH_COORDINATOR_HOME is located.
Next, add the package using the following command.
machcoordinatoradmin --add-package=new_package --file-name=./machbase-ent-new.official-LINUX-X86-64-release-lightweight.tgz
Specifies the name of the package to add.
Specifies the path to the package file to add.
If a package with the same filename is added, you will receive an error, so check the file name.
In the Coordinator, run the following command.
machcoordinatoradmin --upgrade-node=localhost:5656 --package-name=new_package
Enters the name of the upgrade target Node.
Enters the name of the Package to be upgraded.
If you upgrade the Node without shutting down the Node, it will automatically shut down the Node and perform the Node upgrade.
However, for stability, you should explicitly shut down the Node before upgrading.