This guide explains how to move the Zookeeper service to the webapp nodes after upgrading to VeridiumID 3.8.3.
1. Install Zookeeper on Webapp Nodes
After upgrading to 3.8.3, run the installation script on the webapp nodes.
Option A — Using YUM repositories
sudo bash /etc/veridiumid/update-procedure/current/resources/scripts/383/zookeeper_install.sh -i -p PRIMARY_IP_ADDR -s SECONDARY_IP_ADDR
Parameters
-
PRIMARY_IP_ADDR– IP address of the primary node (cluster participant). -
SECONDARY_IP_ADDR– IP address of the secondary node (cluster observer).
Option B — Using local RPM packages
If you are installing from locally downloaded RPM packages, run:
sudo bash /etc/veridiumid/update-procedure/current/resources/scripts/383/zookeeper_install.sh -i -p PRIMARY_IP_ADDR -s SECONDARY_IP_ADDR -r PATH
Parameters
-
PRIMARY_IP_ADDR– IP address of the primary node. -
SECONDARY_IP_ADDR– IP address of the secondary node. -
PATH– Full path to the directory containing the required RPM packages.
2. Create Zookeeper Paths
Run the following command on one webapp node only to create the required Zookeeper paths:
sudo bash /etc/veridiumid/update-procedure/current/resources/scripts/383/zookeeper_install.sh -c
3. Migrate Existing Zookeeper Data
Run the following command on all webapp nodes to:
-
Migrate data from the old Zookeeper cluster
-
Update values in the
zookeeper.propertiesconfiguration file
sudo bash /etc/veridiumid/update-procedure/current/resources/scripts/383/zookeeper_install.sh -m
4. Restart Webapp Services
After migration is complete, restart the required webapp services on all webapp nodes:
LIST=("ver_websecadmin" "ver_tomcat" "ver_selfservice" "ver_fido" "ver_setupagent" "ver_freeradius")
for service_name in ${LIST[@]}; do
service ${service_name} restart
done
✅ After these steps are completed, the Zookeeper service will run on the webapp nodes, and the previous Zookeeper setup can be safely decommissioned if no longer needed.