[GitHub] [druid] licl2014 commented on issue #10242: Coordinator will spend a lot of time(many hours) to assign segments when a historical lost.

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

licl2014 commented on issue #10242:
URL: https://github.com/apache/druid/issues/10242#issuecomment-669228580


   The historical has about 1 million segments, after it lost(whatever offline permanently or just temporarily), coordinator will  assign replicate segments  to other active historicals in the next round scheduling,  but `cost algorithm` is time-consuming ,`replicationThrottleLimit`  and `maxSegmentsInNodeLoadingQueue`  has no effect(historicals load segment faster than coordinator assign segment),so coordinator will hang for hours.
   `Cachingcost` has no such problem,because cachingcost algorithm is very efficient and coordinator assign segment faster than historicals load segment, so `maxSegmentsInNodeLoadingQueue` and `replicationThrottleLimit` has effect. @asdf2014 


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