clintropolis commented on issue #10193: URL: https://github.com/apache/druid/issues/10193#issuecomment-789601179
>from a quick skim over the discussion, solution proposed in #10213 is ok if only one historical was slow/mis-behaving due to a host issue but if this is a cluster level problem then you might not get desired behavior, that solution would end up over allocating segment assignment to historicals, consequently requiring overall "historical cluster" to do more work than what was being done otherwise probably. @himanshug is it the balancer change in that PR that has you worried I guess that it will cause extra data to be pulled from deep storage? I think that if this change were put in place, what you describe could still be mitigated by increasing the timeout or number of threads, but it doesn't seem to terrible for druid to be able to assume the worst and try to have something else load it, and the coordinator won't make false assumptions about historicals maybe having less space than they actual have due to the now phantom loads since the segments are still tracked on the peon. ---------------------------------------------------------------- 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: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
