Upgrade to Version 3.3.0 from Previous Versions

Steps to Migrate from pulse 3.0.x to 3.3.0

Mongo Upgrade Steps

You must ensure that the Mongo migrate steps are present in the Pulse server.

Download Mongo Images By Docker Pull

You must download the Mongo DB images by executing the following command.

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

Download Mongo Migrate Images From Download Links

1. Download the Mongo image which are named as database-4.tar.gz and database-5.tar.gz in the Pulse server
2. After download, execute the following command. This command ensures that the images are loaded to the local repository.

docker load -i

Docker Upgradation Steps

1. Uninstall the current docker by executing the following command.

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

2. Install Docker latest version by executing the following command.

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

To install a specific version of Docker, execute the following command.

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

In the above command, you must replace 24.0.5 with appropriate version string.

To list specific version of Docker, execute the following command.

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

3. Start Docker by executing the following command.

systemctl start docker

Cluster Specific Changes

This section is applicable only if you are upgrading to Pulse 3.3.0 from a version other than 3.2.x.

The following components are not present in Pulse release, lower than 3.2.x compared to Pulse 3.3.0 release.

• ad-events
• ad-gauntlet

Ad-gauntlet does not require any changes to be done on the cluster side. However, introduction of ad-events component requires certain changes related to hooks to be done on the cluster side.

To configure Hive/Tez hooks, you can refer to the (Link Removed) document.

Steps to Upgrade Pulse

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

accelo admin database push-config

3. (IMPORTANT) Ensure that you have downloaded/docker load all the necessary pulse images for Pulse 3.3.0 version.
4. Ensure the pre-requisites for mongo migration/upgradation are performed.
5. Ensure the pre-requisites for docker upgrade are performed.
6. (Optional) Perform the pre-requisites for Cluster specific changes if migrating from Pulse other than 3.2.x.
7. Download the new accelo binary and replace the older accelo binary with the newer one.
8. Execute the migrate command. This command has the following options.

For instance, to migrate from Pulse 3.0.12 to Pulse 3.3.0 version the migrate command is as follows.

accelo migrate -v 3.3.0 -i 3.0.12

9. (OPTIONAL) After the migration command successfully executes, deploy all the core containers by executing the following command.

accelo deploy core

10. Restart all the container so that they use the updated images by executing the following command.

accelo restart all -d

11. Uninstall the hydra agent by executing the following command.

accelo uninstall remote

12. Install the hydra agent by executing the following command.

accelo deploy hydra

13. To push the updated config to the database, execute the following command.

accelo admin database push-config -a

14. Reconfigure the cluster to get the updated configs for agents.

accelo reconfig cluster -a

15. To configure when gauntlet snap will run MongoDB cleanup & compaction, execute the following command.

accelo config retention

When prompted, you must enter the values as a string of comma separated values. For example 12,18.