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/07/10 15:03:43 UTC

[GitHub] [incubator-druid] sashidhar edited a comment on issue #8038: Making optimal usage of multiple segment cache locations

sashidhar edited a comment on issue #8038: Making optimal usage of multiple segment cache locations
URL: https://github.com/apache/incubator-druid/pull/8038#issuecomment-510046061
 
 
   @dclim , @nishantmonu51 Here's what I'm thinking.
   
   As discussed, the segment cache location selector strategy should be configurable. There could be 3 possible strategies currently.
   
   1.  Round-robin selector strategy
   2.  Least bytes used selector strategy
   3.  Current behaviour
   
   Questions:
   1. Default strategy - Should this be the current behaviour which is there right now in production or one of round-robin or least bytes used ?
   2. Property name for the new configuration - how does this sound **druid.segmentCache.locationSelectorStrategy**.  ?
   3. Possible values for the above property - **round-robin**, **least-bytes-used**  ?
   
   Other things to note:
   1. This PR will have to introduce an optional new Historical runtime property. 
   2. Documentation for the same and mention in the release notes. 
   
   @gianm FYI.
   

----------------------------------------------------------------
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