we have druid cluster with 0.9.2.
I found, when there is one or a few historical node suffering full GC or broken, the coordinator node then do the balancing or shuffling on all segments,
but right now, querying to broker is not right, the broker just return the result based on lacking data, which is not actual one.
So are there some tuning things on this case ? Or just avoid full GC?
The docs in http://druid.io/docs/0.9.2/design/coordinator.html about Segment Availability says,
it can set a period of time to reassigned segments to other
historical node, and The lifetime represents a period of time in which the coordinator will not reassign a dropped segment.
But in the coordinator config page, I am not sure the two period time to set, is it millisToWaitBeforeDeleting ?
Thanks in advance.