/opt/weka
directory.weka status
CLI command if there is a data upgrade
task in aRUNNING
state.weka version get <new-version>
where <new-version>
is the name of the new version (e.g.,3.13.0
), followed by weka version prepare <new-version>
. 3.13.0
version from get.weka.io, where a token need to be supplied as, use: curl
command as described in the install tab on the get.weka.io new version release page.install.sh
(useful on environments where there is no connectivity to get.weka.io, such as dark sites or private VPCs).weka local run --in <new-version> upgrade --prepare-only
weka local run --in <new-version> upgrade
<new-version>
is the name of the new version (e.g.,3.13.0
).upgrade
command:--stop-io-timeout
--host-version-change-timeout
--disconnect-stateless-clients-timeout
--prepare-only
--dont-upgrade-clients
weka user login
) to run the upgrade command.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. host-version-change-timeout
to 600
and disconnect-stateless-clients-timeout
to 200 .
--dont-upgrade-clients
flag in the upgrade command will only upgrade the backend servers, leaving the clients in the old version. Since version 3.12.0, the Weka system supports connecting clients from the one version prior and serving IOs in a mixed-version cluster (backends in version N
and clients in version N/N-1
). weka local upgrade
CLI command from the client host.weka status
command.# weka status
Weka v3.13.0
...
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.