Upgrading Earlier Versions#
This page details upgrade instructions for earlier versions.
Upgrades for Squirro 3.4.x to 3.5.2#
These upgrade instructions explain how to update an existing Linux-based Squirro installation to the current version.
Only follow these instructions if a specific Squirro release notes document references these as the correct upgrade instructions.
Before Upgrading#
Maintenance window#
A Squirro upgrade requires downtime. This is typically quite short, but will still affect user experience for a moment. As a result, upgrades to production systems should only be run in a maintenance window.
Storage vs. Cluster Nodes#
Squirro distinguishes between storage and cluster nodes. These can be installed on the same server or split up. Both can also be horizontally scaled and have multiple instances. For full details see How Squirro Scales.
Independent of the setup, in the instructions below always execute all the storage node updates first, and only then do the cluster node updates. This applies independent of whether cluster and storage node are on the same system, whether they are split into one server each, or if they have multiple instances each.
Offline Repository#
If you have used an offline installation, or have an internal mirror of the Squirro yum repository, ensure it is updated prior to starting the Squirro update.
Upgrading#
Storage Nodes#
Run these instructions on every single server that has storage nodes installed before moving on to the cluster nodes.
yum update java-1.8.0-openjdk
# Update ElasticSearch
yum update elasticsearch
# Update storage node
yum update squirro-storage-node-users
yum update squirro-storage-node
Cluster Nodes#
yum update java-1.8.0-openjdk
yum update squirro-cluster-node-users
yum update "squirro-*"
At this point you will have to check if any *.rpmnew files have been created in /etc/squirro. See Upgrading Configuration Conflicts for instructions on how to handle those.
Finally, restart the services:
systemctl reload nginx
squirro_restart
And validate if everything is coming up (this may have to be run a few times until everything stabilizes):
squirro_status
Upgrades for Squirro 3.2.x and 3.3.x#
These upgrade instructions explain how to update an existing Linux-based Squirro installation to the current version.
Only follow these instructions if a specific Squirro release notes document references these as the correct upgrade instructions.
Please ensure that your current version is 3.1.0 or later. Directly upgrading from previous versions is not supported and needs to be done with a stepped approach. Please contact support if you are on a Squirro release older than 3.1.0.
Before Upgrading#
Maintenance window#
A Squirro upgrade requires a downtime. This is typically quite short, but will still affect user experience for a moment. As a result, upgrades to production systems should only be run in a maintenance window.
Storage vs. Cluster Nodes#
Squirro distinguishes between storage and cluster nodes. These can be installed on the same server or split up. Both can also be horizontally scaled and have multiple instances. For full details see How Squirro Scales.
Independent of the setup, in the instructions below always execute all the storage node updates first, and only then do the cluster node updates. This applies independent of whether cluster and storage node are on the same system, whether they are split into one server each, or if they have multiple instances each.
Offline Repository#
If you have used an offline installation, or have an internal mirror of the Squirro yum repository, ensure it is updated prior to starting the Squirro update.
Upgrading#
Storage nodes#
Run these instructions on every single server that has storage nodes installed before moving on to the cluster nodes.
yum update java-1.8.0-openjdk
yum update squirro-storage-node-users
# Update storage node
yum update squirro-storage-node
Cluster nodes#
yum update java-1.8.0-openjdk
yum update squirro-cluster-node-users
yum update "squirro-*"
At this point you will have to check if any *.rpmnew files have been created in /etc/squirro. See Upgrading Configuration Conflicts for instructions on how to handle those.
Finally, restart the services:
systemctl reload nginx
squirro_restart
Remove all orphaned python 2 packages:
yum erase "squirro-python27*"
And validate if everything is coming up (this may have to be run a few times until everything stabilizes):
squirro_status