Upgrade to Version 3.5.2

Before proceeding with the upgrade process, 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.5.x to 3.5.2

Pulse Upgrade Steps (Core Services Server / Addon Services Server)

  1. Update Configuration:

    • Update ImageTag in the $AcceloHome/config/accelo.yml file to 3.5.2.

  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 executable, and check the updated Pulse information.
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. Run the below command to push acceldata.conf and other updated files to MongoDB.
Bash
Copy
  1. Delete the following directories.
Bash
Copy
  1. In case the file $AcceloHome/config/docker/addons/ad-core-connectors.yml is present, edit the file and add the following environment variable to ad-sparkstats.
Bash
Copy
  1. Restart all containers including database(s) with the following command.
Bash
Copy
  1. Uninstall the hydra agent.
Bash
Copy
  1. Reconfigure the cluster to get the updated configurations for agents.
Bash
Copy

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

Migration Steps from Version 3.4.x to 3.5.2

Pulse Upgrade Steps (Core Services Server / Addon Services Server)

  1. Update Configuration:

    • Update ImageTag in the $AcceloHome/config/accelo.yml file to 3.5.2.

  2. Push Updated Configuration to Database:

    • Run the following command:
Bash
Copy

  1. Download Necessary Images:

    • Ensure you have downloaded or loaded all the necessary Docker images for version 3.5.2.

  2. Update Accelo Binary:

    • Download the new Accelo binary.
    • Replace the older Accelo binary with the new one.

  3. Run Migration Command:

  • Make sure you run the command from $AcceloHome.
  • Do not change the value of -v from 3.5.0 unless explicitly advised by Engineering. The following command needs to run on all Pulse nodes including standalone nodes i.e. nodes where PULSE_SA_NODE is true. Examples of such nodes include but aren’t limited to Logsearch, FS Analytics V2, Dashplot .
  • -v: This indicates the version you are migrating to.
  • -i : This indicates the version you are migrating from. For example, to migrate from 3.4.1 to 3.5.0, make sure to run the below command from $AcceloHome.
Bash
Copy
  • For Multi-Cluster:
Bash
Copy

  1. Handle Migration Issues:

    • If any issues occur during migration, rerun the same command.

  2. Restart Containers:

    • Restart all containers to use the updated images:
Bash
Copy
  1. Uninstall Hydra Agent:
    • Run the following command:
Bash
Copy
  1. Install Hydra Agent:
    • Run the following command:
Bash
Copy
  1. If Logsearch is deployed in standalone mode:
    • Check if yarn_app_es_urls is present in override.yml
    • If the above is present, change the port number from 19013 to 19051.
Bash
Copy
  1. Reconfigure Cluster:
    • To get the updated configuration for agents, run:
Bash
Copy
  1. Push Updated Configuration to Database:
    • Run the following command:
Bash
Copy
  1. Configure MongoDB Cleanup & Compaction:
    • To configure when Gauntlet Snap will run MongoDB cleanup and compaction, run:
Bash
Copy
  1. Create Indices for Database Collections:
    • Finally, run the following command.

If readOnlyRootFSEnabled is set to true in $AcceloHome/config/accelo.yml, then follow the steps listed below instead of running the command directly.

1 . Open $AcceloHome/config/accelo.yml and set the value of readOnlyRootFSEnabled to false.

  1. Run accelo admin database push-config
  2. Run accelo restart all -d.
  3. Run accelo admin database index-db.
  4. Open $AcceloHome/config/accelo.yml and set the value of readOnlyRootFSEnabled to true.
  5. Run accelo admin database push-config.
  6. Run accelo restart all -d.
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.

Migration Steps from Version 3.3.x to 3.5.2

Pulse Upgrade Steps (Core Services Server / Addon Services Server)

  1. Update Configuration:
  • Update ImageTag in the $AcceloHome/config/accelo.yml file to 3.5.2.
  1. Push Updated Configuration to Database:
  • Run the following command:
Bash
Copy

  1. Download Necessary Images:

    • Ensure you have downloaded or loaded all the necessary Docker images for version 3.5.2.

  2. Update Accelo Binary:

    • Download the new Accelo binary.
    • Replace the older Accelo binary with the new one.

  3. Run Migration Command:

  • Make sure you run the command from $AcceloHome.
  • Do not change the value of -v from 3.5.0 unless explicitly advised by Engineering. The following command needs to run on all Pulse nodes including standalone nodes i.e. nodes where PULSE_SA_NODE is true. Examples of such nodes include but aren’t limited to Logsearch, FS Analytics V2, and Dashplot.
  • -v: This indicates the version you are migrating to.
  • -i : This indicates the version you are migrating from. For example, to migrate from 3.3.8 to 3.5.0, make sure to run the below command from $AcceloHome.
Bash
Copy
  • For Multi-Cluster:
Bash
Copy

  1. Handle Migration Issues:

    • If any issues occur during migration, rerun the same command.

  2. Delete the following directories.

Bash
Copy
  1. Restart Containers:Restart all containers to 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:
    • Check if yarn_app_es_urls is present in override.yml
    • If the above is present, change the port number from 19013 to 19051.
Bash
Copy
  1. Reconfigure Cluster:
    • To get the updated configuration for agents, run:
Bash
Copy
  1. Push Updated Configuration to Database:
    • Run the following command:
Bash
Copy
  1. Configure MongoDB Cleanup & Compaction:
    • To configure when Gauntlet Snap will run MongoDB cleanup and compaction, run:
Bash
Copy
  1. Create Indices for Database Collections:
    • Finally, run the following command.

If readOnlyRootFSEnabled is set to true in $AcceloHome/config/accelo.yml, then follow the steps listed below instead of running the command directly.

1 . Open $AcceloHome/config/accelo.yml and set the value of readOnlyRootFSEnabled to false.

  1. Run accelo admin database push-config
  2. Run accelo restart all -d.
  3. Run accelo admin database index-db.
  4. Open $AcceloHome/config/accelo.yml and set the value of readOnlyRootFSEnabled to true.
  5. Run accelo admin database push-config.
  6. Run accelo restart all -d.
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
Next to read:
Upgrade to Version 3.5.1

For additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282

Copyright © 2025

On This Page
Upgrade to Version 3.5.2PrerequisiteMigration Steps from Version 3.5.x to 3.5.2Pulse Upgrade Steps (Core Services Server / Addon Services Server)Migration Steps from Version 3.4.x to 3.5.2Pulse Upgrade Steps (Core Services Server / Addon Services Server)Migration Steps from Version 3.3.x to 3.5.2Pulse Upgrade Steps (Core Services Server / Addon Services Server)