helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kishore gopalakrishna (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HELIX-94) Add the ability to enable and disable a resource
Date Wed, 08 May 2013 18:33:16 GMT

    [ https://issues.apache.org/jira/browse/HELIX-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652189#comment-13652189

kishore gopalakrishna commented on HELIX-94:

I thought a little more about it. We might actually have two requirements

1. PAUSE resource: We want to controller to not send any transitions related to a resource.
This may not only be at the start up of the cluster, it might be at any time. Its more like
pause option for the cluster which means controller will not do issue any transitions but
the participant will continue to function normally. This option is useful when some is starting
up the cluster for the first time or do a rolling upgrade. Pausing the controller will avoid
lot of unnecessary transitions.

2. DISABLE resource: This is more like disabling an instance or a partition. It means the
resource should not be hosted on any PARTICIPANT. So if the resource is already hosted on
some PARTICIPANTS controller will bring it back to OFFLINE similar to what it does when an
instance is disabled.

What do you think?
> Add the ability to enable and disable a resource
> ------------------------------------------------
>                 Key: HELIX-94
>                 URL: https://issues.apache.org/jira/browse/HELIX-94
>             Project: Apache Helix
>          Issue Type: Improvement
>          Components: helix-core
>    Affects Versions: 0.6.0-incubating
>            Reporter: Vinayak Borkar
> It would be useful to provide a way to enable and disable resource just as there are
ways to enable/disable partitions and instances.
> Initially, when a new resource is created, it should start in the disabled state. The
user will be required to explicitly enable the resource in order for it to participate in
External View computation. This will provide a clean interface for users to add new resources
and configure them fully before they are made "visible" to the cluster to provide an "atomic"
view of a configured resource.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message