Hi Lei,

Yes, we'd like at most one transition for a partition.

Besides this, we also need instance and cluster level throttling. Can you
take a look at the configuration I posted above. It didn't work for us.
Anything we missed?

Thanks,
Bo

On Feb 16, 2018 08:50, "Lei Xia" <[email protected]> wrote:

> Hi, Bo
>
>   Can you elaborate more on your use case?  Are you saying you do not want
> any offline->slave transition if there is an ongoing Master->Slave
> transition?
>
>
>
> Lei
>
> On Fri, Feb 16, 2018 at 8:20 AM, kishore g <[email protected]> wrote:
>
>> I thought we had throttling support at the partition scope. I will have
>> to check the code and get back to you
>>
>> On Fri, Feb 16, 2018 at 7:55 AM, Bo Liu <[email protected]> wrote:
>>
>>> Your input on how to configure Helix for Throttling is appreciated.
>>>
>>> On Thu, Feb 15, 2018 at 5:09 PM, Bo Liu <[email protected]> wrote:
>>>
>>>> A related question. Is this the proper way to enable instance and
>>>> cluster level throttling?
>>>> Basically we want to allow up to 100 concurrent state transitions at
>>>> cluster level and 2 at instance level.
>>>> This is configured as list fields of cluster configuration.
>>>> It didn't work. So I am wondering what's the proper way to configure it?
>>>>
>>>> Thanks,
>>>> Bo
>>>>
>>>> On Thu, Feb 15, 2018 at 3:18 PM, Bo Liu <[email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Does Helix support throttling state transition at partition level?
>>>>> I only find cluster, resource and instance level throttling as below:
>>>>>
>>>>> public enum ThrottleScope {
>>>>>   CLUSTER,
>>>>>   RESOURCE,
>>>>>   INSTANCE
>>>>> }
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best regards,
>>>>> Bo
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Bo
>>>>
>>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Bo
>>>
>>>
>>
>
>
> --
> Lei Xia
>

Reply via email to