gianm commented on issue #12262: URL: https://github.com/apache/druid/issues/12262#issuecomment-1183684955
> Awesome. with this capability, we can do shuffle joins, window aggregations, etc without bottlenecking on the broker. have you also thought about elasticity? Right now, scaling historicals up and down is tricky for large clusters as segment balancing takes time and historicals need to download segments from deep storage. with elasticity in mind, (1) makes much more sense than (2) This analysis makes sense and I agree (1) makes more sense from an elasticity point of view. As you point out, the historicals are generally going to be more gradually scaled out due to their loaded-up caches. -- 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]
