Date: Thu, 28 Mar 2024 12:04:16 +0000 (UTC) Message-ID: <180126141.37.1711627456139@48d4dacd1130> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_36_669979059.1711627456139" ------=_Part_36_669979059.1711627456139 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Released on April 14, 2016.
Smooth the dashboard switch transitions
Size the grid according to actual widgets dimensions
Please follow the regular installation steps.= p>
To upgrade to version 2.3.3 of Squirro, please ensure that your current = version is at least version 2.3.0 or higher. This is because this version c= ontains a new major version of ElasticSearch. If you are on a version older= than 2.3.0, please contact support.
This is not the latest version of Squirro. To upgrade to this version, p= lease ensure that you point the squirro yum repository to version '2.3.3' a= nd not to 'latest'.
Additionally if you are using Squirro in a Box, ad= ditional steps are involved. In this case we also ask you to contact support= .
If your storage node runs in the same Virtual Machine or Operating Syste= m as your cluster node, skip this step. Otherwise upgrade all storage nodes= one at a time by running:
[squirr= o@storagenode01 ~] sudo yum update
[squirr= o@clusternode01 ~] sudo yum update
Step 1: Prepare the upgrade
It is not possible to update to this version without a service interrupt= ion.
Please note that the order of the following steps is important. = Do not skip any step. If a step fails, do not continue before resolving the= issue.
On each cluster node, run:
root$= monit stop sqclusterd
On eac= h storage node, one after the other, run:
root$= rpm -Uvh --nodeps $(repoquery --location squirro-elasticsearch-templates)<= /pre>
This will update the templates and re-index all indices with the new map= ping v6. This may take a while.
Important note: Do not use yum u= pdate squirro-elasticsearch-templates as that would attempt t= o update Elasticsearch at the same time for which we are not ready until we= first fix the configuration at the beginning of step 4.
root$= rpm -Uvh --nodeps $(repoquery --location elasticsearch)
Elasticsearch will not start as there are configuration conflicts betwee= n the two versions that need to be fixed manually:
warni= ng: /etc/elasticsearch/elasticsearch.yml created as /etc/elasticsearch/elas= ticsearch.yml.rpmnew warning: /etc/init.d/elasticsearch created as /etc/init.d/elasticsearch.rpm= new warning: /etc/sysconfig/elasticsearch created as /etc/sysconfig/elasticsear= ch.rpmnew warning: /usr/lib/systemd/system/elasticsearch.service created as /usr/lib/= systemd/system/elasticsearch.service.rpmnew
Networking behaviour changed with Elasticsearch 2. In a multi-storagenod=
e setup, make sure that the elasticsearch cluster network configuration is =
set up correctly. In a standard setup, adding the following to the
netwo= rk.bind_host: _site_,_local_ network.publish_host: _site_
For further help, please consult https://www.elastic.co/guide/en/elasticsearch/= reference/current/modules-network.html\
Remove the ES plugins as they are no longer compatible (new ones will be= installed by yum update):
root$= rm -rf /usr/share/elasticsearch/plugins/*
And last, index the percolation queries that could not be migrated autom= atically (only required if the file /tmp/elasticsearch/squirro_v5_filt= er.out exists):
root$= curl -s -XPOST http://localhost:9200/_bulk --data-binary "@/tmp/elasticsea= rch/squirro_v5_filter.out"
root$= yum update
Depending on your configuration, Elasticsearch might not come up until y=
ou updated a second storage node as it requires at least two nodes to be pr=
esent.
Depending on your index size, the initial start of elasticsearch service wi=
ll take a while as it migrates the index internally.
On each cluster node, run:
root$ y= um update root$ yum reinstall squirro-python-squirro.api.topic
Resolve /etc/squirro/topic.ini.rpmnew
If you run =
Squirro in a multi-cluster-node environment |
---|
root$= mkdir -p /mnt/gv0/widgets root$ chown -R sqtopic:squirro /mnt/gv0/widgets root$ sed -e 's|^custom_widgets_directory =3D .*|custom_widgets_directory = =3D /mnt/gv0/widgets/|' -i /etc/squirro/topic.ini root$ sed -i -e 's/db_endpoint_discovery =3D false/db_endpoint_discovery = =3D true/' /etc/squirro/topic.ini root$ if [[ ! -L "/var/lib/squirro/topic/widgets" && -d "/var/lib/s= quirro/topic/widgets" ]]; then rm -ir /var/lib/squirro/topic/widgets; fi root$ ln -s /mnt/gv0/widgets /var/lib/squirro/topic/widgets root$ service sqtopicd restart |
Then start Squirro again:
root$= monit start sqclusterd root$ monit start sqfrontendd