Adding a Kafka Broker Instance for Consistency with the Zookeeper
Adding a new Kafka broker has the following prerequisites:
- You will need an available worker node already deployed that does not already have a Kafka broker or ZooKeeper instance deployed on it.
- The new node where a Kafka broker is deployed should be labeled
kafka:yes(on-premises installation), orkafka=yes(for cloud installation). - If you plan to deploy both Kafka Brokers and ZooKeepers , it is recommended that you perform this procedure to add Kafka brokers after you have deployed your ZooKeepers and they are up and running.
To add a Kafka broker:
- Open the CDF Management Portal.
- Click ... (Browse) to the right.
- From the drop-down, select Reconfigure. The post-deployment settings page is displayed.
- Find the field # of Kafka broker nodes in the Kafka cluster.
- From the field's drop-down, select the new number of Kafka brokers.
- Adjust any other related fields as needed. For example, if the topic replication factor is 1, consider increasing it.
- Click Save.
- Verify that the new Kafka brokers are up and in Running state by running the command:
kubectl get pods -n {arcsight_namespace_id} th-kafka-x
Next, assign partitions to the new Kafka broker:
- Connect to Transformation Hub Kafka Manager.
Refer to Connecting to the Kafka Manager for more information.
- In Cluster > Transformation Hub > Topics, click Generate Partition Assignments.
- On the Confirm Assignments page, confirm partition assignments for the new broker and click Generate Partition Assignments.
- On the main toolbar, click Topic > List.
- Click Run Partition Assignments.
- On the Run Assignments page, confirm partition assignments and click Run Partition Assignments.
- The partition reassignment process begins. On the Reassign Partitions page, under Status, check for a date and time of the job completion to verify completion of the task.
Reducing the number of Kafka brokers is not currently supported.