Upgrade From Version 3.0.x to 3.3.0

This document describes the steps to migrate from Pulse 3.0.x version to 3.3.0 version.

Prerequisite

Upgrade Docker to 20.10.x or above. Perform the following steps to upgrade your Docker version:

1. Run the following command to uninstall the current Docker version:

yum remove -y docker-ce docker-ce-cli containerd.io

2. Run the following command to install the latest Docker version:

yum install -y docker-ce docker-ce-cli containerd.io

To install a specific version of Docker, run the following code:

yum install -y docker-ce-24.0.5 docker-ce-cli-24.0.5 containerd.io

To list a specific version of Docker, run the following code:

yum list docker-ce --showduplicates | sort -r

3. Run the following code to start Docker:

systemctl start docker

Steps Required for Migration from 3.0.x to 3.3.0

Upgrade Mongo

Perform the following steps to upgrade Mongo:

1. Run the following code to download the Mongo images by docker pull:

docker pull 191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-database:migrate-4.4.20

docker pull 191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-database:migrate-5.0.16

2. Perform the following steps to download the Mongo images from the download links:
   1. Download the mongo images named database-4.tar.gz and database-5.tar.gz in the Pulse server.
   2. Once the download is completed, run docker load -i for these images to be loaded in the local repository.

Upgrade Docker

Cluster-Specific Updates for Upgrading from Pulse Versions <3.2.X (Other than)

The following components are unique to the 3.3.0 release compared to versions earlier than 3.2.x:

1. ad-events
2. ad-gauntlet

Note that ad-gauntlet does not necessitate any cluster-side modifications. However, the introduction of the ad-events component does require specific changes related to hooks to be made on the cluster side.

For instructions on configuring Hive or Tez hooks, refer to this document: (Link Removed).

Steps to Upgrade Pulse

To upgrade to the latest Pulse version, perform the following steps:

1. Update the ImageTag in the $AcceloHome/config/accelo.yml file to 3.3.0 .
2. Run the following command to push the updated configs:

accelo admin database push-config

3. Important Ensure that you have obtained and loaded all the essential Pulse images for version 3.3.0, either through downloading or Docker.
4. Ensure that you have completed the necessary prerequisites for the Mongo migration or upgrade.
5. Ensure that you have completed the necessary prerequisites for the Docker upgrade.
6. Optional Perform the prerequisites for cluster-specific alterations when migrating from Pulse versions other than 3.2.x.
7. Download the latest accelo binary and substitute the older accelo binary with the latest one.
8. Run the Migrate command with the specified version parameters. For example, to migrate from Pulse version 3.0.12 to 3.3.0, use the following command:

accelo migrate -v 3.3.0 -i 3.0.12

• -v 3.3.0 states that you want to migrate to version 3.3.0.
• -i 3.0.12 specifies that you are migrating from version 3.0.12 to version 3.3.0.

accelo migrate -v 3.3.0 -i 3.0.12 -a

9. If you face any issues during migration rerun the same command.
10. Optional Once the migration command has been successfully executed, proceed to deploy all the containers. Note: This step is only necessary for Pulse versions earlier than 3.2.0.

accelo deploy core

11. Restart all the container in order for them to use the updated images using the following code:

accelo restart all -d

12. Uninstall the hydra agent using the following command:

accelo uninstall remote

13. Install the hydra agent using the following command:

accelo deploy hydra

14. Reconfigure the cluster to get the updated configs for agents using the following command:

accelo reconfig cluster -a

15. Push the updated config to the database by running the following command:

accelo admin database push-config -a

16. Run the following command to configure when gauntlet snap should run MongoDB cleanup and compaction:

accelo config retention

When prompted, values must be provided as a string of comma separated values. For example 12,18