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] [Updated] (HELIX-139) Need to double check the logic to prevent 2 controllers to control the same cluster
Date Mon, 26 Aug 2013 21:10:52 GMT

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

kishore gopalakrishna updated HELIX-139:
----------------------------------------

    Fix Version/s: 0.6.2-incubating
    
> Need to double check the logic to prevent 2 controllers to control the same cluster
> -----------------------------------------------------------------------------------
>
>                 Key: HELIX-139
>                 URL: https://issues.apache.org/jira/browse/HELIX-139
>             Project: Apache Helix
>          Issue Type: Sub-task
>            Reporter: Shi Lu
>            Assignee: dafu
>            Priority: Critical
>             Fix For: 0.6.2-incubating
>
>
> It seems that people can create another controller to a already controlled helix cluster,
the new controller.connect() method did not throw any exceptions
> We should check if we have such testcases.

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

Mime
View raw message