Upgrade to Version 3.7.1

If you are upgrading Pulse from the version 3.5.0 or lower, make sure to export all the custom dashboards from the Pulse UI. For details, see Exporting Dashboards.

Prerequisite

Upgrade the Docker version to 20.10.x or above.

Steps to upgrade the Docker version:

  1. Uninstall the current Docker:
Bash
Copy
  1. Install the latest version of Docker:
Bash
Copy
  • To install a specific version of Docker:
Bash
Copy
  • Replace 24.0.5 with the appropriate version string
  • To list specific versions of docker
Bash
Copy
  1. Start Docker:
Bash
Copy

Migration Steps from Version 3.7.x to 3.7.1

Follow these steps to upgrade Pulse.

  1. Update Configuration:

    • Update ImageTag in the $AcceloHome/config/accelo.yml file to 3.7.1.
  2. Push Updated Configuration to Database:

    • Run the following command:
Bash
Copy
  1. Take a backup of the accelo file and download the latest version for accelo.linux CLI.
  2. Move and make the latest accelo CLI file as an executable. Also, check the updated Pulse information for the following.
Bash
Copy
  1. For the Online installations, run the following command and press 'Y' at the prompt to get the most recent binaries.
Bash
Copy
  1. For the Offline Installations, download all the latest image packs and run the following command to upload the latest images.
Bash
Copy
  1. Run the below command to update and add new keys in vars.yml.
Bash
Copy
  1. [Optional: If AD-LDAP is deployed] Run the following command to generate an encrypted password for the LDAP server connection.
Bash
Copy
  • Enter the plain-text password to generate the encrypted password.
  • Update the bindPW field in /data01/acceldata/config/ldap/ldap.conf with the encrypted value, and add the encryptedPassword = true flag in the same configuration file.
  1. Run the below command to push acceldata.conf and other updated files to MongoDB.
Bash
Copy
  1. Restart all containers including database(s) with the following command.
Bash
Copy
  1. Uninstall the Hydra Agent.
Bash
Copy
  1. Install the Hydra Agent.
Bash
Copy
  1. Reconfigure the cluster to get the updated configurations for Agents.
Bash
Copy

Migration Steps from Version 3.6.x to 3.7.1

Follow these steps to upgrade Pulse.

  1. Update Configuration:

    • Update ImageTag in the $AcceloHome/config/accelo.yml file to 3.7.1.
  2. Push Updated Configuration to Database:

    • Run the following command:
Bash
Copy
  1. Ensure that you have downloaded and loaded all the necessary Docker images for 3.7.1.
  2. Download a new accelo binary and replace the existing one with the new accelo binary.

Ensure that you do not change the value of v from 3.7.0 to anything else unless explicitly advised by Acceldata. The following command needs to run on all the Pulse nodes including standalone nodes i.e. nodes where PULSE_SA_NODE is true. The examples of such nodes include, but aren’t limited to Logsearch, FS Analytics V2, and Dashplot.

  1. Run the migration command. For example:
    1. -v 3.7.0 : The version you are migrating to. Note Keep the version as -v 3.7.0, even when you are migrating to any update release version in 3.7.x.
    2. -i 3.6.2 : The version you are migrating from.
    3. To migrate from version 3.6.2 to 3.7.1, the migration command looks as shown below.

Ensure that you run the following command from $AcceloHome.

For a single cluster:

Bash
Copy

For multi-cluster:

Bash
Copy
  1. Run the same command again, If any issue occurs during migration on any step.
  2. If YARN optimizer is deployed, append the feature flag "enableStaticQueue": true to the ad-graphql section in the ad-core.yml file.
Bash
Copy

After adding the mentioned feature flag, the FEATURE_FLAG environment must look as below. If you have additional FEATURE_FLAG entries, do not need to remove them, just append "enableStaticQueue": true at the end . For example:

Bash
Copy
  1. Restart all the containers so that they use the updated images.
Bash
Copy
  1. Uninstall the Hydra Agent.
Bash
Copy
  1. Install the Hydra Agent.
Bash
Copy
  1. If Logsearch is deployed in standalone mode, verify whether the yarn app es_urls parameter is present in the override.yml file. If it exists, update the port number from 19013 to 19051.
Bash
Copy
  1. Reconfigure the cluster to get the updated configuration for Agents.
Bash
Copy

If your ODP cluster has Kafka 3 installed, you need to run accelo config cluster before performing this step.

  1. [Optional: If AD-LDAP is deployed] Run the following command to generate an encrypted password for the LDAP server connection.
Bash
Copy
  • Enter the plain-text password to generate the encrypted password.
  • Update the bindPW field in /data01/acceldata/config/ldap/ldap.conf with the encrypted value, and add the encryptedPassword = true flag in the same configuration file.
  1. To push the updated configuration to database, execute the following command.
Bash
Copy
  1. To configure when gauntlet snap must run the MongoDB cleanup and compaction, run the following command.
Bash
Copy
  1. Finally execute the following command to create indices for database collections.
Bash
Copy
Bash
Copy
  1. If the older playbooks already present in the node where ad-director is deployed, delete them, and download the latest playbooks tar from the License UI.
    1. Delete the older playbooks using the command: rm -rf $AcceloHome/work/<cluster_name>/director/playbook/*.Replace <cluster_name> with name of the cluster where the playbooks are present.
    2. Download the playbooks tar from the License UI. For details, see Deploy Playbooks.

Migration Steps from Version 3.5.x to 3.7.1

Follow these steps to upgrade Pulse.

  1. Update Configuration:

    • Update ImageTag in the $AcceloHome/config/accelo.yml file to 3.7.1.
  2. Push Updated Configuration to Database:

    • Run the following command:
Bash
Copy
  1. Ensure that you have downloaded and loaded all the necessary Docker images for 3.7.1.
  2. Download a new accelo binary and replace the existing one with the new accelo binary.

Ensure that you do not change the value of v from 3.7.0 to anything else unless explicitly advised by Acceldata. The following command needs to run on all the Pulse nodes including standalone nodes i.e. nodes where PULSE_SA_NODE is true. The examples of such nodes include, but aren’t limited to Logsearch, FS Analytics V2, and Dashplot.

  1. Run the migration command. For example:
    1. -v 3.7.0 : The version you are migrating to. Note Keep the version as -v 3.7.0, even when you are migrating to any update release version in 3.7.x.
    2. -i 3.5.2 : The version you are migrating from.
    3. To migrate from version 3.5.2 to 3.7.1, the migration command looks as shown below.

Ensure that you run the following command from $AcceloHome.

For a single cluster:

Bash
Copy

For multi-cluster:

Bash
Copy
  1. Run the same command again, If any issue occurs during migration on any step.
  2. Delete the following directories, if they are re present.

This step is applicable only if you are upgrading Pulse from 3.5.0.

Bash
Copy
  1. Delete the metric groups from the alerts collection in MongoDB. Log into Mongo db and run following commands. Note For details about logging into MongoDB, reach out to Acceldata Support.
Bash
Copy
  1. If YARN optimizer is deployed, append the feature flag "enableStaticQueue": true to the ad-graphql section in the ad-core.yml file.

After adding the mentioned feature flag, the FEATURE_FLAG environment must look like this. If you have additional FEATURE_FLAG entries, do not need to remove them, just append "enableStaticQueue": true at the end . For example:

Bash
Copy
Bash
Copy
  1. Restart all the containers so that they use the updated images.
Bash
Copy
  1. Uninstall the Hydra Agent.
Bash
Copy
  1. Install the Hydra Agent.
Bash
Copy
  1. If Logsearch is deployed in standalone mode, verify whether the yarn app es_urls parameter is present in the override.yml file. If it exists, update the port number from 19013 to 19051.
Bash
Copy
  1. Reconfigure the cluster to get the updated configuration for Agents.
Bash
Copy

If your ODP cluster has Kafka 3 installed, you need to run accelo config cluster before performing this step.

  1. [Optional: If AD-LDAP is deployed] Run the following command to generate an encrypted password for the LDAP server connection.
Bash
Copy
  • Enter the plain-text password to generate the encrypted password.
  • Update the bindPW field in /data01/acceldata/config/ldap/ldap.conf with the encrypted value, and add the encryptedPassword = true flag in the same configuration file.
  1. To push the updated configuration to database, execute the following command.
Bash
Copy
  1. To configure when gauntlet snap must run the MongoDB cleanup and compaction, run the following command.
Bash
Copy
  1. Finally execute the following command to create indices for database collections.
Bash
Copy
Bash
Copy
  1. If the older playbooks already present in the node where ad-director is deployed, delete them, and download the latest playbooks tar from the License UI.
    1. Delete the older playbooks using the command: rm -rf $AcceloHome/work/<cluster_name>/director/playbook/*.Replace <cluster_name> with name of the cluster where the playbooks are present.
    2. Download the playbooks tar from the License UI. For details, see Deploy Playbooks.

You can import the previously exported custom dashboards. For details, see Importing Dashboards.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard