You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@helix.apache.org by "Kanak Biscuitwala (JIRA)" <ji...@apache.org> on 2013/11/13 02:23:18 UTC

[jira] [Updated] (HELIX-139) Need to double check the logic to prevent 2 controllers to control the same cluster

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

Kanak Biscuitwala updated HELIX-139:
------------------------------------

    Fix Version/s:     (was: 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: Zhen Zhang
>            Priority: Critical
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)