Acceldata
Pulse

Last updated: Sep 27, 2026 17:49 UTC

Upgrade from V3.3.4, V3.3.5 to V3.3.8

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

Upgrade Steps from Pulse V3.3.4, V3.3.5, to V3.3.8

  • Update Configuration: Change the ImageTag in $AcceloHome/config/accelo.yml to 3.3.8.
  • Push Configuration Update: Execute accelo admin database push-config -a to update the configuration in the database.
  • Back Up and Update CLI:
  • Back up the current accelo file. Download and update to the latest accelo.linux CLI version.
  • Make the new accelo CLI executable with:
mv accelo.linux accelo
chmod +x ./accelo
  • Online Installations: Log in to Docker and download the latest binaries:
accelo login docker
accelo pull all
  • Confirm the download by pressing 'Y' when prompted.
  • Offline Installations: Download the latest image packs. Use docker load -i to upload the latest images.
  • Update Configuration Files: Apply new keys in vars.yml and push updated configurations with:
accelo reconfig cluster
accelo admin database push-config
  • Restart Containers: Restart all containers, including databases, using accelo restart all -d.
  • Manage Hydra Agent:
  • Uninstall any existing hydra agent with accelo uninstall remote.
  • Install the hydra agent afresh with accelo deploy hydra.
  • Finalize Upgrade: Reconfigure the cluster to apply updated configurations for agents by running accelo reconfig cluster -a.


Optional Migration Steps for Pulse Versions Below 3.3.6

These steps are relevant for Pulse installations prior to version 3.3.6 that include an Oozie Server using Oracle DB for metadata storage.

  • Edit Configuration File: Navigate to $AcceloHome/config and open the acceldata_<clustername>.conf file for editing with:
vi $AcceloHome/config/acceldata_<clustername>.conf
  • Modify Oozie Connector Configuration: Locate the oozie.connectors section. Initially, it appears as follows:
oozie.connectors = [
{
 name = "oozie-connector"
 type = "others"
 queryBatchLimit = 100
 thread.pool.size = 10
 pollIntervalMins = 2
 driver = "oracle.jdbc.OracleDriver"
 url = "jdbc:oracle:thin:@//<OOZIE DB HOST>:<OOZIE DB PORT>/xe?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false"
 user = "oozie"
 pass = "BIfSPHgYPE8iZ+0eJI+5yg=="
 encrypted = true
 timezone = "Asia/Kolkata"
 }
]
  • Update the type from others to oracle to reflect the use of Oracle DB. The modified section would look like:
oozie.connectors = [
{
 name = "oozie-connector"
 type = "oracle"
 queryBatchLimit = 100
 thread.pool.size = 10
 pollIntervalMins = 2
 driver = "oracle.jdbc.OracleDriver"
 url = "jdbc:oracle:thin:@//<OOZIE DB HOST>:<OOZIE DB PORT>/xe?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false"
 user = "oozie"
 pass = "BIfSPHgYPE8iZ+0eJI+5yg=="
 encrypted = true
 timezone = "Asia/Kolkata"
 }
]
  • Save Changes: After making the adjustments, save and close the file.
  • Apply Configuration Update: To finalize the changes, execute accelo reconfig cluster to reconfigure the cluster with the updated settings. The Oozie connectors will appear as follows:
oozie.connectors = [
{
 name = "oozie-connector"
 type = "oracle"
 queryBatchLimit = 100
 thread.pool.size = 10
 pollIntervalMins = 2
 driver = "oracle.jdbc.driver.OracleDriver"
 url = "jdbc:oracle:thin:@//<OOZIE DB HOST>:<OOZIE DB PORT>/xe?TNS_ADMIN=/etc/adw"
 user = "oozie"
 pass = "BIfSPHgYPE8iZ+0eJI+5yg=="
 encrypted = true
 timezone = "Asia/Kolkata"
 }
]