Upgrade to Version 3.5.3
Important
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:
- Uninstall the current Docker:
yum remove -y docker-ce docker-ce-cli containerd.io
- Install the latest version of Docker:
yum install -y docker-ce docker-ce-cli containerd.io
- To install a specific version of Docker:
yum install -y docker-ce-24.0.5 docker-ce-cli-24.0.5 containerd.io
- Replace 24.0.5 with the appropriate version string
- To list specific versions of docker
yum list docker-ce --showduplicates | sort -r
- Start Docker:
systemctl start docker
Migration Steps from Version 3.5.x to 3.5.3
Follow these steps to upgrade Pulse.
- Update Configuration:
- Update
ImageTagin the [INLINE_CODE]$AcceloHome/config/accelo.yml[/INLINE_CODE] file to [INLINE_CODE]3.5.3[/INLINE_CODE].
- Update
- Push Updated Configuration to Database:
- Run the following command:
accelo admin database push-config -a
- Take a backup of the
accelofile and download the latest version for [INLINE_CODE]accelo.linux[/INLINE_CODE] CLI. - Move and make the latest
acceloCLI file executable, and check the updated Pulse information.
mv accelo.linux accelo
chmod +x ./accelo
- 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
- Run the below command to update and add new keys in
vars.yml.
accelo reconfig cluster
- Run the below command to push
acceldata.confand other updated files to MongoDB.
accelo admin database push-config
- Delete the following directories (This is applicable only if you are upgrading from Pulse
3.5.0).
rm -rf $AcceloHome/data/pg/*
rm -rf $AcceloHome/data/pg-ui/*
- In case the file
$AcceloHome/config/docker/addons/ad-core-connectors.ymlis present, edit the file and add the following environment variable to [INLINE_CODE]ad-sparkstats.[/INLINE_CODE]
OTEL_JAVAAGENT_ENABLED=false
- Restart all containers including database(s) with the following command.
accelo restart all -d
- Uninstall the hydra agent.
accelo uninstall remote
- Install the Hydra Agent.
accelo deploy hydra
- Reconfigure the cluster to get the updated configurations for agents.
accelo reconfig cluster -a
Important
You can import the previously exported custom dashboards. For details, see Importing Dashboards.
Migration Steps from Version 3.4.x to 3.5.3
Follow these steps to upgrade Pulse.
- Update Configuration:
- Update
ImageTagin the [INLINE_CODE]$AcceloHome/config/accelo.yml[/INLINE_CODE] file to [INLINE_CODE]3.5.3[/INLINE_CODE].
- Update
- Push Updated Configuration to Database:
- Run the following command:
accelo admin database push-config
- Download Necessary Images:
- Ensure you have downloaded and loaded all the necessary Docker images for version
3.5.3.
- Ensure you have downloaded and 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:
Important
- Make sure you run the command from $AcceloHome.
- Do not change the value of
-vfrom [INLINE_CODE]3.5.0[/INLINE_CODE] unless explicitly advised by Engineering. The following command needs to run on all Pulse nodes including standalone nodes i.e. nodes wherePULSE_SA_NODEistrue.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. To migrate from 3.4.1 to 3.5.3, make sure to run the command below from
$AcceloHome.
accelo migrate -v 3.5.0 -i 3.4.1 -a
- For Multi-Cluster:
accelo migrate -v 3.5.0 -i 3.4.1 -a -b
- Handle Migration Issues:
- If any issues occur during migration, rerun the same command.
- Delete the following Directories:
rm -rf $AcceloHome/data/pg/*
rm -rf $AcceloHome/data/pg-ui/*
- Restart Containers:
- Restart all containers to use the updated images:
accelo restart all -d
- Uninstall Hydra Agent:
- Run the following command:
accelo uninstall remote
- Install Hydra Agent:
- Run the following command:
accelo deploy hydra
- If Logsearch is deployed in standalone mode:
- Check if
yarn_app_es_urlsis present in [INLINE_CODE]override.yml[/INLINE_CODE] - If the above is present, change the port number from
19013to [INLINE_CODE]19051[/INLINE_CODE].
- Check if
yarn_app_es_urls: <http://<LOG_SEARCH_HOSTNAME>>:19051
- Reconfigure Cluster:
- To get the updated configuration for agents, run:
accelo reconfig cluster -a
- Push Updated Configuration to Database:
- Run the following command:
accelo admin database push-config -a
- Configure MongoDB Cleanup & Compaction:
- To configure when Gauntlet Snap will run MongoDB cleanup and compaction, run:
accelo config retention
- Create Indices for Database Collections:
- Finally, run the following command.
Important
If readOnlyRootFSEnabled is set to [INLINE_CODE]true[/INLINE_CODE] in [INLINE_CODE]$AcceloHome/config/accelo.yml[/INLINE_CODE], then follow the steps listed below instead of running the command directly.
1 . Open $AcceloHome/config/accelo.yml and set the value of [INLINE_CODE]readOnlyRootFSEnabled[/INLINE_CODE] to [INLINE_CODE]false.[/INLINE_CODE]
- 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 of [INLINE_CODE]readOnlyRootFSEnabled[/INLINE_CODE] to [INLINE_CODE]true.[/INLINE_CODE] - Run
accelo admin database push-config. - Run
accelo restart all -d.
accelo admin database index-db
- 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.
- Delete the older playbooks using the command:
rm -rf $AcceloHome/work/<cluster_name>/director/playbook/*.Replace [INLINE_CODE]<cluster_name>[/INLINE_CODE] with name of the cluster where the playbooks are present. - Download the playbooks tar from the License UI. For details, see Deploy Playbooks.
- Delete the older playbooks using the command:
Important
You can import the previously exported custom dashboards. For details, see Importing Dashboards.
Migration Steps from Version 3.3.x to 3.5.3
Follow these steps to upgrade Pulse.
- Update Configuration:
- Update
ImageTagin the [INLINE_CODE]$AcceloHome/config/accelo.yml[/INLINE_CODE] file to [INLINE_CODE]3.5.3[/INLINE_CODE].
- Push Updated Configuration to Database:
- Run the following command:
accelo admin database push-config
- Download Necessary Images:
- Ensure you have downloaded or loaded all the necessary Docker images for version
3.5.3.
- 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:
Important
- Make sure you run the command from $AcceloHome.
- Do not change the value of
-vfrom [INLINE_CODE]3.5.0[/INLINE_CODE] unless explicitly advised by Engineering. The following command needs to run on all Pulse nodes including standalone nodes i.e. nodes wherePULSE_SA_NODEistrue. 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.3, make sure to run the below command from
$AcceloHome.
accelo migrate -v 3.5.0 -i 3.3.8 -b
- For Multi-Cluster:
accelo migrate -v 3.5.0 -i 3.3.8 -a -b
- Handle Migration Issues:
- If any issues occur during migration, rerun the same command.
- Delete the following directories.
rm -rf $AcceloHome/data/pg/*
rm -rf $AcceloHome/data/pg-ui/*
- **Restart Containers:**Restart all containers to use the updated images:
accelo restart all -d
- Uninstall the Hydra Agent:
accelo uninstall remote
- Install the Hydra agent:
accelo deploy hydra
- If Logsearch is deployed in standalone mode:
- Check if
yarn_app_es_urlsis present in [INLINE_CODE]override.yml[/INLINE_CODE] - If the above is present, change the port number from
19013to [INLINE_CODE]19051[/INLINE_CODE].
- Check if
yarn_app_es_urls: <http://<LOG_SEARCH_HOSTNAME>>:19051
- Reconfigure Cluster:
- To get the updated configuration for agents, run:
accelo reconfig cluster -a
- Push Updated Configuration to Database:
- Run the following command:
accelo admin database push-config -a
- Configure MongoDB Cleanup & Compaction:
- To configure when Gauntlet Snap will run MongoDB cleanup and compaction, run:
accelo config retention
- Create Indices for Database Collections:
- Finally, run the following command.
Important
If readOnlyRootFSEnabled is set to [INLINE_CODE]true[/INLINE_CODE] in [INLINE_CODE]$AcceloHome/config/accelo.yml[/INLINE_CODE], then follow the steps listed below instead of running the command directly.
1 . Open $AcceloHome/config/accelo.yml and set the value of [INLINE_CODE]readOnlyRootFSEnabled[/INLINE_CODE] to [INLINE_CODE]false.[/INLINE_CODE]
- 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 of [INLINE_CODE]readOnlyRootFSEnabled[/INLINE_CODE] to [INLINE_CODE]true.[/INLINE_CODE] - Run
accelo admin database push-config. - Run
accelo restart all -d.
accelo admin database index-db
- 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.
- Delete the older playbooks using the command:
rm -rf $AcceloHome/work/<cluster_name>/director/playbook/*.Replace [INLINE_CODE]<cluster_name>[/INLINE_CODE] with name of the cluster where the playbooks are present. - Download the playbooks tar from the License UI. For details, see Deploy Playbooks.
- Delete the older playbooks using the command:
Important
You can import the previously exported custom dashboards. For details, see Importing Dashboards.

Have a suggestion?