jtuglu-netflix commented on PR #18176: URL: https://github.com/apache/druid/pull/18176#issuecomment-3025142092
@clintropolis now that segments are being cached on historicals, and intra-AZ requests are much faster than S3 reads (intra-AZ requests are typically XXXµs, whereas S3 is ~500 ms tail latency for single RTT not to mention the numerous RTT from downloading massive segments), is there any idea to make historicals basically a distributed caching tier? i.e historical A can pull from B for col C from segment D? -- 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]
