Cruise-control is the first of its kind to fully automate the dynamic workload rebalance and self-healing of a Kafka cluster. It provides great value to Kafka users by simplifying the operation of Kafka clusters.
I was looking in the docs but couldn't quite find an answer. Let's say I have a cluster of 3 nodes (one in each rack). I create another three nodes (0ne in each rack) and run a rebalance (with rack awareness) to remove the first 3. Will the data from each node be transferred to the node on the same rack, or will it be random and match the goal of the rebalance (in this case, rack awareness)? I appreciate any help you can provide.
I was looking in the docs but couldn't quite find an answer. Let's say I have a cluster of 3 nodes (one in each rack). I create another three nodes (0ne in each rack) and run a rebalance (with rack awareness) to remove the first 3. Will the data from each node be transferred to the node on the same rack, or will it be random and match the goal of the rebalance (in this case, rack awareness)? I appreciate any help you can provide.