A new installation of either Control-M/Enterprise Manager or Control-M/Server version 9.0.21 on Windows in a cluster fails to add Kafka and Zookeeper services to the resource group and as a result when a failover or move is performed to switch the active node of the cluster, the Kafka and Zookeeper services do not behave properly |
This issue is resolved in version 9.0.21.100. Use the following steps after the installation of Control-M/Enterprise Manager and Control-M/Server 9.0.21.000 to prevent the Kafka/Zookeeper startup failure until you are able to upgrade to 9.0.21.100 or higher: 1) Stop all Control-M/Enterprise Manager and/or Control-M/Server Cluster resources via the Windows Cluster Manager 2) Verify no Control-M/Enterprise Manager and/or Control-M/Server processes are running If necessary kill process that are still running 3) Open a Powershell session and execute the following: For Control-M/Enterprise Manager : cd "<EM_HOME>\bin"
.\CTMUpadteCluster_V21.ps1 install EM For Control-M/Server :
cd "<CTM_HOME>\scripts"
.\CTMUpdateCluster_V21.ps1 install CTM 4) Restart the Cluster manager service on ALL cluster nodes. Open a command prompt and execute the following:
net stop clussvc && net start clussvc
5) Start all Control-M/Enterprise Manager and/or Control-M/Server resources from the cluster manager 6) Set the Control-M Web Server Desired State to "Ignored". For Control-M/Enterprise Manager, run the following command:
em updater -cluster_components 9.0.21.000
For Control-M/Server
No action is required |