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 2014/08/25 19:38:58 UTC

[jira] [Updated] (HELIX-350) cluster status monitor should not be reset in FINALIZE type pipeline

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

Kanak Biscuitwala updated HELIX-350:
------------------------------------

    Fix Version/s: 0.6.4
                   0.7.1

> cluster status monitor should not be reset in FINALIZE type pipeline 
> ---------------------------------------------------------------------
>
>                 Key: HELIX-350
>                 URL: https://issues.apache.org/jira/browse/HELIX-350
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Shi Lu
>            Assignee: Shi Lu
>            Priority: Critical
>             Fix For: 0.7.1, 0.6.4
>
>
> Currently, the cluster status monitor is disposed when the controller is running a FINALIZE type pipeline, which is possible when a participant is down (which make the controller no-longer listen to its current state change and will trigger FINALIZE type pipeline)
> the change is to dispose the cluster status monitor when the controller helix manager disconnects from zookeeper.



--
This message was sent by Atlassian JIRA
(v6.2#6252)