Acceldata
Pulse

Last updated: Sep 28, 2026 11:14 UTC

Upgrade from Version 3.0.3 to 3.0.3-1

This document explains the steps to migrate from Pulse v3.0.3 to 3.0.3-1. This document is applicable only to Pulse users who are using the Pulse v3.0.3. For a fresh Pulse installation, you must download the container images for the ad-deployer and ad-hydra for 3.0.3-1, retag and use it with Pulse Version 3.0.3.

For the Pulse 3.0.3-1 version, only the ad-deployer and ad-hydra containers are built.

Migration Steps

Warning

  • Requires re-installation of Pulse agents running in all the cluster nodes.

Please plan your migrations accordingly.

  • Downloadad-deployer and ad-hydra with tag 3.0.3-1.
  • Retag both the containers by executing the following commands.
docker tag 191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-hydra:3.0.3-1 191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-hydra:3.0.3
docker tag 191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-deployer:3.0.3-1 191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-deployer:3.0.3
  • Restart the hydra server by executing the following command.
accelo restart ad-hydra
  • (Optional) If one or more nodes are impacted by hystaller, related to the /etc/passwd parsing issue, they can reinstall the agents by executing the following command or by using the Cloudera Parcel-based deployment.
accelo deploy hydra