Updating LogScale
This guide will take you through the steps required to update your LogScale cluster to a newer version.
You should always check the Release Notes for all versions between the version of LogScale you are currently running and the version you are installing.
Important
When upgrading, all notes in the cluster should be updated to the same version. Although running different versions on different nodes may work, it is not a supported deployment configuration.
The recommended method for updating a whole LogScale requires updating the whole cluster at the same time to the new version. This requires downtime for the clsuter as the entire will need to be offline to complete the upgrade. The basic process is as follows:
Stopping data ingestion
Shutting down each node
Updating each node to the new version of LogScale
Start up each node in the cluster
Updating a Node
Updating LogScale is a matter of stopping the old running version and starting the new version, on top of the same data directories, and with the same configuration, in most cases. Some releases have instructions in their release notes on required steps to update, but most releases should run on top of the previous one.
We recommend that you make a backup copy of the file
$DATA_DIR/humio-data/global-data-snapshot.json
before you update — preferably after shutting down the old version
but before starting the new one. This file can be used to roll back to
the previous version if necessary.
Updating LogScale Running in Docker
When using Docker images to run LogScale, update by pulling the latest version of the Docker image and running it using the same Docker arguments as previously.
All LogScale images are tagged with a version:
latest
— the latest stable version of LogScalestable
— the latest stable version of LogScalepreview
— the latest preview version of LogScale
In the example below, latest
is used as version to
update the single image Docker version, where everything is inside a
single Docker container.
$ docker stop humio
|
| true
$ docker rm humio
|
| true
$ docker pull humio/humio:latest
$ docker run \
-v $YOUR_LOGSCALE_URL_DATA_DIR:/data \
--net=host \
--detach \
--restart=always \
--name=humio \
--stop-timeout 300 \
--env-file=$PATH_TO_CONFIG_FILE humio/humio
Updating LogScale Running from tar.gz
When using tar.gz downloads from Maven download archives to run LogScale, update by following these steps.
Download the tarball.
Terminate LogScale:
shell$
cd /var/humio
$ps -ef|grep humio|awk '{ print $1 }'|xargs kill
Delete
humio/bin
andhumio/libs
directories:shell$
rm -rf bin libs
Extract the new tarball:
shell$
cd /var
$tar zxf server-1.142.1.tar.gz
Restart the service. If done manually from the terminal, execute the following command (does not apply for LogScale instances run by services like systemd):
shell$
cd /var/humio
$./bin/humio-server-start.sh
Updating LogScale Running in Kubernetes
If running the LogScale Operator, see the Upgrading LogScale Operator on Kubernetes documentation.
If running the LogScale Helm Chart, see the Upgrading with Kubernetes section of the Helm Chart documentation page.
Warning
This is generally not recommended for version updates but is convenient for configuration changes.
Update the
values.yaml
file with the new configuration.Update the statefulset/pods with the new configuration by running:
logscalehelm upgrade --values values.yaml humio humio/humio-helm-charts