Title
Create new category
Edit page index title
Edit category
Edit link
Upgrade to Version 3.5.0
Prerequisite
Upgrade the Docker version to 20.10.x or above.
Steps to upgrade the Docker version:
- Uninstall the current Docker:
- Install the latest version of Docker:
- To install a specific version of Docker:
- Replace 24.0.5 with the appropriate version string
- To list specific versions of docker
- Start Docker:
Migration Steps from Version 3.4.x to 3.5.0
Follow these steps to upgrade Pulse (Core Services Server or Addon Services Server).
Update Configuration:
- Update
ImageTagin the$AcceloHome/config/accelo.ymlfile to3.5.0.
- Update
Push Updated Configuration to Database:
- Run the following command:
Download Necessary Images:
- Ensure you have downloaded or loaded all the necessary Docker images for version
3.5.0.
- Ensure you have downloaded or loaded all the necessary Docker images for version
Update Accelo Binary:
- Download the new Accelo binary.
- Replace the older Accelo binary with the new one.
Run Migration Command:
- Make sure you run the command from $AcceloHome.
- Do not change the value of
-vfrom3.5.0unless explicitly advised by Engineering. The following command needs to run on all Pulse nodes including standalone nodes i.e. nodes wherePULSE_SA_NODEis true. Examples of such nodes include but aren’t limited toLogsearch,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.
- For Multi-Cluster:
Handle Migration Issues:
- If any issues occur during migration, rerun the same command.
Restart Containers:
- Restart all containers to use the updated images:
- Uninstall Hydra Agent:
- Run the following command:
- Install Hydra Agent:
- Run the following command:
- If Logsearch is deployed in standalone mode:
- Check if
yarn_app_es_urlsis present inoverride.yml - If the above is present, change the port number from
19013to19051.
- Check if
- Reconfigure Cluster:
- To get the updated configuration for agents, run:
- Push Updated Configuration to Database:
- Run the following command:
- Configure MongoDB Cleanup & Compaction:
- To configure when Gauntlet Snap will run MongoDB cleanup and compaction, run:
- 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.
- Run
accelo admin database push-config - Run
accelo restart all -d. - Run
accelo admin database index-db. - Open
$AcceloHome/config/accelo.ymland set the value ofreadOnlyRootFSEnabledtotrue. - Run
accelo admin database push-config. - Run
accelo restart all -d.
- If the old playbooks already present in the node where ad-director is deployed, delete them, and download the latest playbooks tar from the License UI.
- Delete the old 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. - Download the playbooks tar from the License UI.
- Delete the old playbooks using the command:
Migration Steps from Version 3.3.x to 3.5.0
Follow the steps below to upgrade Pulse.
- Update Configuration:
- Update
ImageTagin the$AcceloHome/config/accelo.ymlfile to3.5.0.
- Push Updated Configuration to Database:
- Run the following command:
Download Necessary Images:
- Ensure you have downloaded or loaded all the necessary Docker images for version
3.5.0.
- Ensure you have downloaded or loaded all the necessary Docker images for version
Update Accelo Binary:
- Download the new Accelo binary.
- Replace the older Accelo binary with the new one.
Run Migration Command:
- Make sure you run the command from $AcceloHome.
- Do not change the value of
-vfrom3.5.0unless explicitly advised by Engineering. The following command needs to run on all Pulse nodes including standalone nodes i.e. nodes wherePULSE_SA_NODEis true. Examples of such nodes include but aren’t limited toLogsearch,FS Analytics V2, andDashplot.
- -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.
- For Multi-Cluster:
Handle Migration Issues:
- If any issues occur during migration, rerun the same command.
Restart Containers:
- Restart all containers to use the updated images:
- Uninstall the Hydra Agent:
- Install the Hydra agent:
- Restart Containers:
- Restart all containers to use the updated images:
- If Logsearch is deployed in standalone mode:
- Check if
yarn_app_es_urlsis present inoverride.yml - If the above is present, change the port number from
19013to19051.
- Check if
- Reconfigure Cluster:
- To get the updated configuration for agents, run:
- Push Updated Configuration to Database:
- Run the following command:
- Configure MongoDB Cleanup & Compaction:
- To configure when Gauntlet Snap will run MongoDB cleanup and compaction, run:
- Create Indices for Database Collections:
- Finally, run the following command.
- If the old playbooks already present in the node where ad-director is deployed, delete them, and download the latest playbooks tar from the License UI.
- Delete the old 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. - Download the playbooks tar from the License UI.
- Delete the old playbooks using the command:
For additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026