Upgrade from Pulse V3.3.4, 3.3.5 to V3.3.7
Before performing the steps to upgrade from Pulse V3.3.4 or V3.3.5 to V3.3.7, ensure you have followed the steps provided in the prerequisite section of this document.
Prerequisite
Ensure that your Docker version is updated to 20.10.x or higher. To upgrade, perform the following:
- 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, run the following code and replace the 24.0.5 with the appropriate version string
:
yum install -y docker-ce-24.0.5 docker-ce-cli-24.0.5 containerd.io
To list a specific version of Docker, run the following code:
yum list docker-ce --showduplicates | sort -r
- Start Docker:
systemctl start docker
Steps to Upgrade from Pulse V3.3.4 or 3.3.5 to V3.3.7
To upgrade from Pulse versions V3.3.4 and V3.3.5 to V3.3.7, perform the following:
- Update the
ImageTag
in$AcceloHome/config/accelo.yml
to3.3.7
- Push the updated config to the database, by executing the following command:
accelo admin database push-config -a
- Move the accelo.linux file to accelo and make it executable using the command chmod +x ./accelo. Then, verify the updated Pulse information.
mv accelo.linux accelo
chmod +x ./accelo
- For 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 Offline Installations, download all the latest image packs and run the following command to upload the latest images:
docker load -i
- Update and add new keys in
vars.yml
:
accelo reconfig cluster
- Push
acceldata.conf
and other updated files to MongoDB:
accelo admin database push-config
- Restart all containers, including database(s):
accelo restart all -d
- Uninstall the hydra agent:
accelo uninstall remote
- Install the hydra agent:
accelo deploy hydra
- Finally, reconfigure the cluster to get the updated configs for agents:
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 theacceldata_<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:
x
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
fromothers
tooracle
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"
}
]
Was this page helpful?