klsince commented on PR #9624: URL: https://github.com/apache/pinot/pull/9624#issuecomment-1284707605
A new target tier can lead to two reactions: 1) segment needs to go to a new server (when the target tier is only defined for a specific pool of servers as identified via `serverTag` in the tierConfig); 2) segment is already on the right server, but still needs to go to a new tier, backed by a different datadir. Action 1 is handled by TableRebalancer; Action 2 is handled by SegmentReloadMessage. Extending SegmentRelocator, it's easy to control the sequence of those two actions, to do Action 2 after Action 1 is completed. So that, we don't send SegmentReloadMessage to a server that's not the ideal server for the segment yet, and it reloads the segment unnecessarily. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
