wirybeaver commented on issue #11278: URL: https://github.com/apache/pinot/issues/11278#issuecomment-1680079174
I notice there's a commit to support tenant rebalancing. https://github.com/apache/pinot/commit/d6b1b4feba1f9a2168f5119e1b673d7cfcf8d146 To be generic, Pinot does't perfectly support add new nodes. When a new node join the tenant, regardless of it's a broker or server for a long while (e.g., 30mins), the rebalancing should be auto triggered whatever the underlying infra (ec2, k8s) holding pinots. Otherwise, each infra need to add a post processing workflow to trigger the tenant rebalancing after spinning up a new node. In addition, pool based segment assignment strategy requires to trigger an api in order to assign **new** segments onto new nodes, which is even worse than the balanced assignment strategy. https://github.com/apache/pinot/issues/10181 Wanted to collect all related issues to raise awareness on making pinot Cloud Native, i.e. smoothly support capacity change. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
