Before upgrading your cluster, ensure the following:
All backend hosts are online.
Any rebuild has been completed.
The WekaIO upgrade process supports upgrading to both higher minor versions and major versions of the WekaIO software.
When upgrading to a major version, always upgrade to the latest minor version in the new major version. This may require first upgrading to a specific minor version in the current software version, as follows:
To upgrade to WekaIO software version 3.5.x, go through version 3.4.6 or above.
To upgrade to WekaIO software version 3.4.x, go through version 3.3.1 or above.
To upgrade to WekaIO software version 3.3.x, go through version 3.2.1 or above.
To upgrade to WekaIO software version 3.2.x, go through version 220.127.116.11 or above.
For further information, contact the WekaIO Support Team.
Download the new release on one of the backend hosts, as follows:
SSH into one of the backend hosts of the cluster.
Go to https://get.weka.io and navigate to the release to be downloaded.
wget command line on the backend host.
Untar the downloaded package.
install.sh script of the new release.
From WekaIO software version 3.5 onwards, the disruptiveness of the upgrade procedure is limited to a defined window of 10 minutes. WekaIO system guarantees that either the upgrade process to the new version finishes successfully or the version is automatically reverted to the old one within this window.
In case of a failure, the version is automatically reverted on the hosts, yet,
weka cluster start-io command should be run manually after verifying all hosts have indeed been reverted to the old version by running
weka cluster host command.
Once a new software version is installed on one of the backend hosts, the cluster has to be upgraded to the new release. This is performed by running the following command on the backend host:
weka local run --in <new-version> upgrade --mode one-shot
<new-version> is the name of the new version downloaded from get.weka.io, e.g.,
The limited upgrade window can be controlled by setting the following parameters in the
Parameters in Command Line
Maximum time in seconds to wait for IO to successfully stop
Maximum time in seconds to wait for a host version update
Maximum time in seconds to wait for IO to successfully start
Download and prepare a new software version across all hosts in the cluster, without performing the actual upgrade
Before switching the cluster to the new release, the upgrade command will distribute the new release to all cluster hosts and make any necessary preparations, such as compiling the new
wekafs driver. If any failure occurs during the preparations, such as disconnection of a host or failure to build a driver, the upgrade process will stop and a summary message will be received indicating the problematic host.
If everything goes to plan, the upgrade will stop the cluster IO service, switch all hosts to the new release and then turn the IO service back on. This takes about 1 minute, depending on the size of the cluster.
Once the upgrade is complete, verify that the cluster is in the new version by running the
weka status command.
WekaIO version 3.5 provides performance improvements when working with object stores. To reap the benefits of improved object store performance and ensure the conversion of the internal WekaIO data structure, the following is recommended for each tiered filesystem when upgrading from version 3.4 to version 3.5:
Attach a new object store bucket.
Delete any unnecessary snapshots (so unnecessary data is not copied to the new bucket).
Detach the old object store bucket.
Perform all necessary checks to ensure that data is copied to the new object store bucket.
Re-upload relevant snapshots to the new object store bucket in order to re-create the snapshot locator on that bucket.