Upgrading Weka Versions
Before upgrading your cluster, ensure the following:
All backend hosts are online.
Any rebuild has been completed.
There no outstanding alerts that haven't been addressed.
There are at least 4GB free in the
/opt/wekadirectory.
The Weka upgrade process supports upgrading to both higher minor versions and major versions of the Weka 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 Weka software version 3.11.x, go through version 3.10.0 or above
To upgrade to Weka software version 3.10.x, go through version 3.9.0 or above
To upgrade to Weka software version 3.9.x, go through version 3.8.0 or above
To upgrade to Weka software version 3.8.x, go through version 3.7.3 or above
For further information, contact the Weka Support Team.
Download and prepare the new release on one of the backend hosts, using one of the following methods:
From the backend host, run
weka version get <new-version>where<new-version>is the name of the new version (e.g.,3.11.0), followed byweka version prepare <new-version>.If you don't have a distribution server set, you can add it explicitly to the command. For example, to get the
3.11.0version from get.weka.io, where a token need to be supplied as, use:
weka version get 3.11.0 --from https://[GET.WEKA.IO-TOKEN]@get.weka.ioFrom the backend host, run the
curlcommand as described in the install tab on the get.weka.io new version release page.Download the new version tar file to the backend host and run
install.sh(useful on environments where there is no connectivity to get.weka.io, such as dark sites or private VPCs).
Once the Weka cluster upgrade is called, it will first prepare all the connected hosts (clients and backends) for the upgrade, which includes downloading the new version and get it ready to be applied. Only then, it will start the upgrade process of the cluster. This reduces to a minimum any downtime that the client host can experience from the Weka cluster.
Although not needed, and distribution of the new version to the hosts should be fast as part of the upgrade, when working with a large number of hosts it is possible to prepare for this in advance, separated from the cluster upgrade (e.g., to shorten the total upgrade window).
First, obtain the new version on one of the backend host, as described above, then, use the following CLI command:
weka local run --in <new-version> upgrade --mode one-shot --prepare-only
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
where <new-version> is the name of the new version (e.g.,3.11.0).
The limited upgrade window can be controlled by setting the following parameters in the upgrade command:
Parameters in Command Line
Name | Type | Value | Limitations | Mandatory | Default |
| Integer | Maximum time in seconds to wait for IO to successfully stop | ​ | No | 90 |
| Integer | Maximum time in seconds to wait for a host version update | ​ | No | 180 |
| Integer | Maximum time in seconds to wait for stateless clients to be marked as DOWN and continue the upgrade without them | ​ | No | 60 |
| Boolean | Download and prepare a new software version across all hosts in the cluster, without performing the actual upgrade | ​ | No | False |
Note: When using non-default passwords, run this command with the environment variables. For example:
weka local run --in <new-version> -e WEKA_USERNAME=<user> -e WEKA_PASSWORD=<passwd> upgrade --mode=one-shot
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 the 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.
Note: In large deployments of Weka with many backend hosts and hundreds/thousands of clients it might be required to adjust the above timeouts.
It is recommended then to set host-version-change-timeout to 600 and disconnect-stateless-clients-timeout to 200 .
If further assistance and adjustments are required please contact the Weka Support Team.
Once the upgrade is complete, verify that the cluster is in the new version by running the weka status command.
For Example: The following will be received when the system has been upgraded to version 3.11.0:
# weka status
Weka v3.11.0
...
The disruptiveness of the upgrade procedure is limited to a defined window of 10 minutes. Weka system ensures 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.