Upgrade From Version 3.1.1 to 3.2.0

This document describes the steps to migrate from Pulse version 3.1.1 to Pulse version 3.2.0. You must perform the steps mentioned in this document in all your clusters.

Backup Steps

1. Take backup of Dashplots Charts using Export option.

2. Take backup of Alerts using the Export option.

MongoDB Upgrade

Execute the following command to updated the Mongo DB to latest version 6.0.5.

accelo admin database migrate

Regular Migration Steps

1. Update the ImageTag in the $AcceloHome/config/accelo.yml file to 3.2.0.
2. To push the updated config to the database, execute the following command.

accelo admin database push-config -a

3. Take a backup of the accelo file and download the latest version for accelo.linux CLI.
4. Move and make the latest accelo cli file executable, and check the updated Pulse information for the following.

mv accelo.linux accelo

chmod +x ./accelo

5. Perform the action in one of the following columns based on whether you are doing an online or offline installation.

6. Execute the following command to update and add new keys in the vars.yml file.

accelo reconfig cluster

7. Execute the following command to update the override.yml file.

accelo migrate -v 3.2.0

8. Execute the following command to push acceldata.conf and other updated files to MongoDB.

accelo admin database push-config

9. Restart all containers including database(s) with the following command.

accelo restart all -d

10. Uninstall the hydra agent.

accelo uninstall remote

11. Install the hydra agent.

accelo deploy hydra

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

accelo admin database push-config -a

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

accelo reconfig cluster -a

14. Disable the Remote JMX Port in PulseJMX Agent.
    1. Edit the override.yml file.
       1. Add the following code to the override.yml file.

enable_jmx_remote_port: "false"

This disables the remote port option for the pulsejmx agent.

b. Execute the reconfig cluster command.

accelo reconfig cluster -a

Pulse Hooks Deployment

Pulse now uses the NATS queue. To get the streaming data from NATS, you must configure and deploy the JAR files in various folders. Based on the configuration you use, you can refer to the respective sections (Hive, tez etc) for hook configuration. The links to each section are as follows.

• HDP 2.x, 3,x, and ODP 3.2.x
• CDH 5.x and 6.x
• CDP 7.x

Connector Level Configurations

This section describes the configurations you must perform on various connector microservices for Pulse deployments.

Sparkstats

You must generate the required connectors YAML file, if not available. You can execute the following command to generate the YAML file.

accelo admin makeconfig ad-core-connectors

Configuration for Sparkstats

You must configure the ad-core-connectors.yml file. To accomplish this, you must add the following environment variable under ad-sparkstats.

NATS_SERVER_HOST_LIST=(PULSE_IP:19009)

YARN applications and Hive-queries

You must perform the following configuration in Pulse configurations, under individual collectors.

nats.server.host.list = "(PULSE_IP:19009)" 

​

# You must use appropriate value for port number, applicable to your setup.