You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/03/04 20:06:30 UTC

[GitHub] [incubator-druid] leventov commented on issue #7186: Caffeine-based remote cache with adaptive admission windows

leventov commented on issue #7186: Caffeine-based remote cache with adaptive admission windows
URL: https://github.com/apache/incubator-druid/issues/7186#issuecomment-469402364
 
 
   Segments are served by multiple historicals, and although currently Brokers almost never take advantage of that, there are multiple reasons why they should start query different historicals more often (identified, for example, in [this post](https://medium.com/@leventov/the-problems-with-druid-at-large-scale-and-high-load-part-1-714d475e84c9), and also mentioned in the issue about [online aggregation](https://medium.com/@leventov/the-problems-with-druid-at-large-scale-and-high-load-part-1-714d475e84c9)). Thus the same segment might have separate be tracked in several independent admission windows on different historicals. If this is a big obstacle for the idea and how it can be solved (randomization?) is yet to be determined.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org