Hello Team, I'm seeking clarification regarding data rebalancing in a Pinot cluster deployed on Amazon Elastic Kubernetes Service (EKS). Currently, our Pinot servers are running within pods on EKS. Each server pod is responsible for handling specific table segments. My question pertains to the scenario where a new server pod is deployed due to scaling. Is there an internal mechanism provided by Pinot or ZooKeeper that automatically rebalances existing data segments from the older two servers to the newly deployed third server? In other words, when a new server comes online, will it automatically take over some of the existing data segments, thereby reducing the load on the two older servers? Without such a mechanism, the benefit of scaling out servers would be diminished, as new servers wouldn't actively participate in handling the existing data workload. Any insights or documentation regarding this behavior would be greatly appreciated. Thank you!

Hi Kavan, rebalancing isn't happening automatically for now it's a manual process which needs to be planned and performed by user https://docs.pinot.apache.org/operators/operating-pinot/rebalance/rebalance-servers

Okay, Thank you for the providing the reference. @Aleksandrs Vedernikovs