Hello team, a quick question on pool-based instanc...
# general
s
Hello team, a quick question on pool-based instance assignment. Currently the instance assignment will be persisted into InstancePartitions and used for segment assignment. How does it handle capacity change? For example, I want to add more servers for a tenant. Do I need to trigger reassign instances? Do you have recommendation for best practice? Thanks. cc: @Xuanyi Li
m
You add more nodes, tag them appropriately (with pool tag) and rebalance your tables.
x
trigger rebalance table by table is not convenient. Ideally, when a node is registered with a tenant tag and become alive for a configurable time period, the segments should automatically rebalanced. Druid did that way. I do understand there’s some concern on the reliability of rebalancing, but given that capacity change is a common daily operation in the cloud, I think Pinot should support auto rebalancing feature.
this feature almost fits my need. Basically, when a new node join the tenant for a long while, the tenant rebalance should be triggered automatically.