[GitHub] [druid] himanshug edited a comment on issue #9816: Historical rack aware (or group aware) data replication

[GitBox <gi...@apache.org>]

himanshug edited a comment on issue #9816:
URL: https://github.com/apache/druid/issues/9816#issuecomment-716747133


   > for a case where number of groups or racks = number of replicas desired, sure. But a large enterprise cluster will have 10s of racks and will not want a replica on every rack due to cost concerns. 
   
   that should be possible I think.
   
   say, you have 4 racks/groups/tiers ... A, B, C, D
   
   with config...
   
   ```
     "tieredReplicants": {
         "A": 1,
         "B" : 2
     }
   ```
   
   number of replicants != number of tiers , and not every replica is on each tier.
   
   or maybe I misunderstood above statement.
   
   > And trying to automatically generate load rules that properly balance datasources across those groups by selecting tiers would be burdensome and likely hard to do well.
   
   Yeah, things could possibly be simplified but use of tiers does let you achieve the end goal. Just wanted to point out the existing alternative and also, if possible, it would be nice if tier based grouping could be enhanced to take care of additional use cases or simplification instead of introducing another way of grouping historical.
   


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



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