Upgrading

This section details the steps necessary to upgrade the UiPath High Availability Add-on, including upgrading each respective node and the HAA database(s).

Upgrading a Node

Note: Before and after the upgrade, verify that each node is functioning properly by running: rlcheck, and rladmin status extra all.

1. Download the node upgrade script by running: wget http://download.uipath.com/haa/2.0.1/haa-2.0.1.tar.gz.
2. Unpack the script by running: tar -xf haa-2.0.1.tar.gz.
3. Make the script executable: chmod a+x install.sh.
4. Run the script: sudo ./install.sh.

Note: To enable Interactive Mode, run sudo ./install.sh. Alternatively, you can add the -y parameter to respond yes to all.

Upgrading a Database

Important: First make sure that all nodes in the HAA cluster are upgraded. You cannot upgrade databases before all of the nodes in the cluster are upgraded.

From the rladmin CLI on any node in the cluster, run this command for each database: rladmin upgrade db <db-name>.

Note:

During the database upgrade process, the database is restarted. As a result:

• For databases that have replication enabled, a failover is done before the master database restarts to make sure that there is no downtime.

• For databases without replication but with persistence enabled, the database is unavailable during the restart because data is restored from the persistence file. The length of the downtime is different for each persistence option. For example, AOF usually takes longer than an RDB file.

• For databases that have neither replication nor persistence enabled, the database loses all its data after it is restarted.

Upgrading Active-Active Databases

Note:

• Upgrade all instances of a specific CRDB within a reasonable time frame to avoid temporary inconsistencies between the instances.

• Make sure that you upgrade all instances of a specific CRDB before you do global operations on the CRDB, such as removing instances or adding new instances.

1. Upgrade the HAA version on each node in the clusters where the CRDB instances are located.
2. To see the status of your CRDB instances, run: rladmin status. The status of the CRDB instances on the node can indicate one of three options:
   • OLD REDIS VERSION
   • OLD CRDB PROTOCOL VERSION
   • OLD CRDB FEATURESET VERSION
3. To upgrade each CRDB instance, including the Redis version and CRDB protocol version, run: rladmin upgrade db <crdb_name>. If the protocol version is old, read the warning message carefully and confirm.
   
   

   

   
   
4. If the feature set version is old, you must first upgrade all of the CRDB instances. Then, to update the feature set for each active-active database, run: crdb-cli crdb update --crdb-guid <crdb_guid> --featureset-version yes.
5. You can then retrieve the crdb_guid with the following command: crdb-cli crdb list.
6. Look for the fully qualified domain name (CLUSTER-FQDN) of your cluster and use the associated GUID:

   CRDB-GUID	NAME	REPL-ID	CLUSTER-FQDN
   700140c5-478e-49d7-ad3c-64d517ddc486	aatest	1	aatest1.example.com
   700140c5-478e-49d7-ad3c-64d517ddc486	aatest	2	aatest2.example.com