Addition of another server to the Kafka cluster fails after the only server that was part of the Kafka cluster is decommissioned
For ZooKeeper:
Stop all the ZENworks services on the Primary Server on which the ZooKeeper role is enabled. For more information, see Stopping the ZENworks Services.
Remove the zookeeper.properties file from the path %ZENWORKS_HOME%\novell\ZENworks\conf (on Windows) or /etc/opt/novell/ZENworks/conf (on Linux).
Remove the ZooKeeper data directory from the path %ZENWORKS_HOME%\novell\ZENworks\work\zookeeper (on Windows) or /var/opt/novell/ZENworks/zookeeper (on Linux).
Restart all the ZENworks services. For more information, see Starting the ZENworks Services.
For Kafka:
Stop all the ZENworks services on the server on which the zman command to add the Kafka broker was executed but failed. For more information, see Stopping the ZENworks Services.
Remove the Kafka data directory from the path /var/opt/novell/zenworks/kafka-data.
Restart all the ZENworks services. For more information, see Starting the ZENworks Services.
NOTE:If the replication count is 1, then before decommissioning the last server that has a Kafka role enabled in it, run the zman server-role-kafka-add-broker (zman srkab) to add a new broker and then proceed with the decommissioning of the existing server.
However, if you have already decommissioned the server, ensure that you bring up a server with the same hostname by backing up and restoring the Kafka data. For more information, see Replacing an Existing Primary Server with a New Primary Server in the ZENworks Disaster Recovery Reference.
At least one Kafka connector has failed
You can retrieve the names of the all connectors within the command line utility by running the zman server-role-kafka-list-connectors command.
After reconfiguring the Kafka connectors, you need to restart the Kafka-connect service by running the following command:
systemctl restart zenworks-connect.service
systemctl restart microfocus-connect.service