Upgrade to Version 4.1.0

You can follow the appropriate steps to upgrade Pulse to version 4.1.0 based on your current deployment:

• Upgrade Pulse from Version 4.0.x to 4.1.0
• Upgrade Pulse from Version 3.8.x. to 4.1.0

Note Before upgrading Pulse, ensure that your Docker version is upgraded. For details, see Upgrade Prerequisite.

Upgrade Pulse from Version 4.0.x to 4.1.0

This section describes the required steps to upgrade from Pulse 4.0.x to 4.1.0.

Step 1: Update Container Runtime Configuration (Required Only for 4.0.0)

Update the /etc/profile.d/ad.sh file based on your container runtime.

For Podman:

export CONTAINER_TOOL='podman'

export REGISTRY_AUTH_FILE=${AcceloHome}/config/podman/config.json

For Docker:

export CONTAINER_TOOL='docker'

Once modified, run the following command to apply the updated environment variables.

source /etc/profile.d/ad.sh

Step 2: Uninstall Hydra Agent

Hydra agents must be uninstalled to stop NATS stream data from being sent.

SSH-based deployment

accelo uninstall remote

Mpack and parcel-based deployments

• Uninstall Hydra agents from the CDP or Ambari UI.
• This step is required to stop NATS streams from being sent from agents side. Before doing further steps, ensure all NATS stream data has been processed before continuing.

Step 3: Update Accelo CLI

1. Take a backup of the existing accelo CLI binary.
2. Download the latest accelo.linux CLI.
3. Replace the existing binary and make it executable:

mv accelo.linux accelo

chmod +x ./accelo

Step 4: Update the Image Tag

Update the ImageTag in $AcceloHome/config/accelo.yml:

$AcceloHome/config/accelo.yml

Set the version to:

ImageTag: 4.1.0

Push the updated configuration to the database:

accelo admin database push-config -a

Verify the update:

accelo info

Step 5: Offline Installations: Load Latest Images

For offline installations, download the latest image packs and load them:

docker load -i <image-pack>.tar

Step 6: Run Migration

Run the migration command from $AcceloHome.

For example:

• -v: specifies the version you are migrating to (4.1.0). Note: Keep the version as -v 4.1.0, even when you are migrating to any update release version in 4.1.x.
• -i: specifies the version you are migrating from (4.0.0).

To migrate from version 4.0.0 to 4.1.0, the migration command looks as shown below.

For a single cluster, run:

accelo migrate -v 4.1.0 -i 4.0.0 -b

For multi-cluster setups, run:

accelo migrate -v 4.1.0 -i 4.0.0 -a -b

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

Step 7: Online Installations: Pull Latest Images

For online installations, run:

accelo login docker

accelo pull all

Press Y when prompted to download the most recent binaries.

Step 8: Restart Containers

Restart all containers to use the updated images:

accelo restart all -d

Step 9: (Optional) Migrate from old Actions (ad-director) to the new Actions service

Pulse does not support Kerberos migration from old actions to new actions. For new actions, the Kerberos plugin had to be added before running any action plugin if the cluster was kerberized.

1. If the ad-director was previously configured, verify that the new Actions Service (ad-axnserver) container is running.

docker ps -a | grep axnserver

2. If the Actions Service container is not present, deploy it using the command:

accelo deploy addons

3. When prompted, select Actions Service.

? Select the components you would like to install:

  [ ]  ALFRED

  [ ]  Acceldata SQL Analysis service

> [x]  Actions Service

  [ ]  Airflow Connector

  [ ]  Alerts (Agents MUST be configured)

  [ ]  Anomaly Detection

  [ ]  CONFIG SERVER DB

4. Press Enter to start deployment.

Verify the deployment

After deployment completes, confirm that the container is running:

docker ps -a | grep axnserver

Expected output (status should be Up):

abc123def456   acceldata/ad-axnserver:4.1.0   "/opt/..."   Up 2 minutes   0.0.0.0:19999->19999/tcp   ad-axnserver_default

Check the container logs to confirm that the service has started successfully:

docker logs -f ad-axnserver_default

Reconfigure Notifications

If notifications (Email, Slack, Jira) were configured in ad-director, enable them again for the new Actions service.

accelo config actions notifications

Example:

? Select the notifications you would like to enable:

  [ ]  slack

> [x]  email

  [ ]  jira

​

Enter the JODA Timezone value (Example: Asia/Jakarta): Asia/Jakarta

Enter Email DefaultToEmailIds (comma separated list): x, y

After configuration completes:

• The notifications configuration file is generated.
• The configuration is pushed to the Pulse database.

Run the migration

Once the Actions Service is running and healthy, run:

accelo migrate actions

Step 10: Install Hydra Agent

1. Deploy Hydra agents:

accelo deploy hydra

For mpack- or parcel-based deployments, install the Hydra agent using Ambari or Cloudera Manager.

2. Reconfigure the cluster to apply the updated agent configuration:

accelo reconfig cluster -a

3. Push the updated configuration to the database:

accelo admin database push-config -a

Step 11: (Optional) Enable native SSL in Pulse UI

• If SSL was previously enabled using ad-proxy, enable native SSL support in Pulse UI.
• The ad-proxy service has been removed starting in Pulse 4.1.x. Native SSL must now be configured directly in Pulse UI.
• For instructions, see Native SSL/TLS Support for Pulse Web UI.

Step 12: Configure Retention

To configure MongoDB cleanup and compaction scheduling:

accelo config retention

Step 13: Create Database Indices

Run the following command to create indices for database collections:

accelo admin database index-db

If readOnlyRootFSEnabled is set to true in $AcceloHome/config/accelo.yml, follow these steps:

1. Open $AcceloHome/config/accelo.yml and set:

readOnlyRootFSEnabled: false

2. Run:

accelo admin database push-config

accelo restart all -d

accelo admin database index-db

3. Reset readOnlyRootFSEnabled to true and rerun:

accelo admin database push-config

accelo restart all -d

Upgrade Pulse from Version 3.8.x. to 4.1.0

Step 1: Update Container Runtime Configuration

Update /etc/profile.d/ad.sh based on the container orchestration tool in use.

For Docker:

export CONTAINER_TOOL='docker'

For Podman:

export CONTAINER_TOOL='podman'

export REGISTRY_AUTH_FILE=${AcceloHome}/config/podman/config.json

Once modified, run the following command to apply the updated environment variables.

source /etc/profile.d/ad.sh

Step 2: Uninstall Hydra Agent

Hydra agents must be uninstalled to stop NATS stream data from being sent.

SSH-based deployment

accelo uninstall remote

Mpack and parcel-based deployments

• Uninstall Hydra agents from the CDP or Ambari UI.
• Ensure all NATS stream data has been processed before continuing.

Step 3: Update Accelo CLI

1. Take a backup of the existing Accelo binary.
2. Download the latest accelo.linux CLI.
3. Replace the binary and make it executable:

mv accelo.linux accelo

chmod +x ./accelo

Step 4: Update ImageTag

Update the ImageTag in:

$AcceloHome/config/accelo.yml

Set:

ImageTag: 4.1.0

Push the updated configuration to the database:

accelo admin database push-config -a

Verify the update:

accelo info

Step 5: Offline Installations: Load Latest Images

For offline installations, download the latest image packs and load them:

docker load -i <image-pack>.tar

Step 7: Run Migration

For example:

• -v: specifies the version you are migrating to (4.1.0). Note: Keep the version as -v 4.1.0, even when you are migrating to any update release version in 4.1.x.
• -i: specifies the version you are migrating from (3.8.0).

To migrate from version 3.8.0 to 4.1.0, the migration command looks as shown below.

• For a single cluster, run:

accelo migrate -v 4.1.0 -i 3.8.0 -b

• For multi-cluster setups, run:

accelo migrate -v 4.1.0 -i 3.8.0 -a -b

If any issues occur, rerun the same migration command.

Step 8: Deploy Core Services

After migration, deploy core services:

accelo deploy core

Step 9: Online Installations: Pull Latest Images

For online installations:

accelo login docker

accelo pull all

Press Y when prompted to download the latest binaries.

Step 10: Restart Containers

Restart all containers to apply the updated images:

accelo restart all -d

Step 11: (Optional) Migrate from old Actions (ad-director) to the new Actions service

1. If the ad-director was previously configured, verify that the new Actions Service (ad-axnserver) container is running.

docker ps -a | grep axnserver

2. If the Actions Service container is not present, deploy it using the command:

accelo deploy addons

3. When prompted, select Actions Service.

? Select the components you would like to install:

  [ ]  ALFRED

  [ ]  Acceldata SQL Analysis service

> [x]  Actions Service

  [ ]  Airflow Connector

  [ ]  Alerts (Agents MUST be configured)

  [ ]  Anomaly Detection

  [ ]  CONFIG SERVER DB

4. Press Enter to start deployment.

Verify the deployment

After deployment completes, confirm that the container is running:

docker ps -a | grep axnserver

Expected output (status should be Up):

abc123def456   acceldata/ad-axnserver:4.1.0   "/opt/..."   Up 2 minutes   0.0.0.0:19999->19999/tcp   ad-axnserver_default

Check the container logs to confirm that the service has started successfully:

docker logs -f ad-axnserver_default

Reconfigure Notifications

If notifications (Email, Slack, Jira) were configured in ad-director, enable them again for the new Actions service.

accelo config actions notifications

Example:

? Select the notifications you would like to enable:

  [ ]  slack

> [x]  email

  [ ]  jira

​

Enter the JODA Timezone value (Example: Asia/Jakarta): Asia/Jakarta

Enter Email DefaultToEmailIds (comma separated list): x, y

After configuration completes:

• The notifications configuration file is generated.
• The configuration is pushed to the Pulse database.

Run the migration

Once the Actions Service is running and healthy, run:

accelo migrate actions

Step 11: Install Hydra Agent

Deploy Hydra agents:

accelo deploy hydra

Reconfigure the cluster:

accelo reconfig cluster -a

Push updated configuration to the database:

accelo admin database push-config -a

Step 12: (Optional) Enable native SSL in Pulse UI

• If SSL was previously enabled using ad-proxy, enable native SSL support in Pulse UI.
• The ad-proxy service has been removed starting in Pulse 4.1.x. Native SSL must now be configured directly in Pulse UI.
• For instructions, see Native SSL/TLS Support for Pulse Web UI.

Step 12: Configure Retention

To configure MongoDB cleanup and compaction:

accelo config retention

Step 13: Create Database Indexes

Create database indexes:

accelo admin database index-db

If readOnlyRootFSEnabled Is Set to true

If readOnlyRootFSEnabled is enabled in $AcceloHome/config/accelo.yml, perform the following steps:

1. Set readOnlyRootFSEnabled to false.
2. Push configuration and restart:

accelo admin database push-config

accelo restart all -d

3. Create indexes:

accelo admin database index-db

4. Set readOnlyRootFSEnabled back to true.
5. Push configuration and restart again:

accelo admin database push-config

accelo restart all -d