We tried to disable it through helix ui and restful api. Yes, I think it's not caused by the delay feature. Because the disabled resource stayed at online state forever.
On Feb 16, 2018 08:48, "Lei Xia" <[email protected]> wrote: > Hi, Bo > > Disable a resource will bring all of its partitions to OFFLINE. How did > you disable the resource? After disable the resource, do you see state > transition messages sent to the instances which holds the partitions. > > DelayedRebalancer won't delay the resource disable, but instance > disable, i.e, if you disable an instance, all partitions on that instance > will be moved away only after the delay timeout. > > > Lei > > On Fri, Feb 16, 2018 at 8:42 AM, kishore g <[email protected]> wrote: > >> Disable should move all partitions to OFFLINE state. This might be a bug >> with DelayedRebalancer. Lei, do you know more about this? >> >> On Fri, Feb 16, 2018 at 7:54 AM, Bo Liu <[email protected]> wrote: >> >>> >>> We'd like to change all partitions of a resource to Offline state and >>> then let Helix to gradually move them to Online state. This will help us >>> easily refresh the dataset hosted on the resource. >>> We tried to disable&enable the resource. It doesn't change the states of >>> any partitions. So I guess it only disables Helix management for the >>> resource? >>> >>> -- >>> Best regards, >>> Bo >>> >>> >> > > > -- > Lei Xia >
