Created on 10-19-2022 09:53 AM - edited 10-19-2022 09:54 AM
Hi all, this may be an easy question, but just wanted to verify. When adding new brokers to the cluster, after installing the Kafka role/instance on the new hosts, should you start the new broker instances first before you restart the existing brokers? Or does it matter? This is CDP Private Cloud 7.1.7
Thanks
Created on 10-19-2022 10:51 AM - edited 10-19-2022 10:52 AM
Want to get a detailed solution you have to login/registered on the community
Register/LoginCreated 10-19-2022 10:48 AM
AFAIU It should not matter. You can choose the rolling restart option as well. So CM can decide the sequence of the broker restarts.
Created on 10-19-2022 10:51 AM - edited 10-19-2022 10:52 AM
Want to get a detailed solution you have to login/registered on the community
Register/LoginCreated 10-19-2022 11:01 AM
Thanks. I think I can use Cruise Control to re-distribute the partitions across the new brokers. Haven't tried yet though.
Created on 10-19-2022 11:13 AM - edited 10-19-2022 11:22 AM
Yes, you can use the CC APIs as per your requirements [1] [2]
From the above articles you can use the following API to rebalance topics/partitions:
curl -k --negotiate -u: -X POST "https://<CC FQDN>:8899/kafkacruisecontrol/rebalance?dryrun=false&rebalance_disk=true"
To avoid high CPU, memory and disk read write you can initiate rebalance process in batches. It will automatically create a batch and rebalance topics.
curl -X POST "http://$HOSTNAME:8899/kafkacruisecontrol/rebalance?dryrun=true&concurrent_partition_movements_per_broker=10&concurrent_leader_movements=500"
If it will help you then please click on ”Accept as Solution" below this post.
Thank you.