Upgrade from Version 3.0.3 to 3.1.1

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

If you are using Pulse 3.0.0, you cannot migrate from Pulse 3.0.0 to 3.1.1 directly. You must first migrate to 3.0.3 and then migrate to 3.1.1. To learn more about how to migrate from pulse 3.0.0 to 3.0.3, see Upgrade Pulse from 3.0.0 to 3.0.3.

Backup Steps

Take backup of Dashplots Charts using Export option.

Take backup of Alerts using the Export option.

Migration Steps

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

Bash
    
 
accelo admin database push-config -a
Copy

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

Bash
    
 
mv accelo.linux accelochmod +x ./accelo
Copy

Perform one of the following steps based on whether you are doing an online or offline installation.

Online Installation	Offline Installation
For the online installations, run the following command and press 'Y' at the prompt to get the most recent binaries. `accelo login docker` `accelo pull all`	For the Offline Installations download all the latest image packs and run the following command to upload the latest images. `docker load -i`

Restart all containers including database(s) by executing the following command.

Bash
    
 
accelo restart all -d
Copy

Uninstall the hydra agent:

Bash
    
 
accelo uninstall remote
Copy

Install the hydra agent.

Bash
    
 
accelo deploy hydra
Copy

Reconfigure the cluster to get the updated configs for agents.

Bash
    
 
accelo reconfig cluster -a
Copy

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.

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.

Bash
    
​x
 
nats.server.host.list = "(PULSE_IP:19009)" ​# You must use appropriate value for port number, applicable to your setup.
Copy

Last updated on

Was this page helpful?