You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "Shi Lu (JIRA)" <ji...@apache.org> on 2013/02/13 01:11:15 UTC

[jira] [Updated] (HELIX-25) setConfig should check if instance exist or not when setting PARTICIPANT config

     [ https://issues.apache.org/jira/browse/HELIX-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shi Lu updated HELIX-25:
------------------------

    Assignee: dafu  (was: Shi Lu)
     Summary: setConfig should check if instance exist or not when setting PARTICIPANT config  (was: enableInstance should check if instance exist or not)

We need to make sure that setConfig does nothing when setting a participant config which is not added into cluster yet. As some code in helix use the childnames of /CONFIGS/PARTICIPANT  to get the list of instances in the cluster
                
> setConfig should check if instance exist or not when setting PARTICIPANT config
> -------------------------------------------------------------------------------
>
>                 Key: HELIX-25
>                 URL: https://issues.apache.org/jira/browse/HELIX-25
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Shi Lu
>            Assignee: dafu
>             Fix For: 0.6.1-incubating
>
>
> If enableInstance is called with a non-exist instance name, it will succeed and create config for the instance; and subsequent addInstance can fail.

--
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