helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shi Lu (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HELIX-350) cluster status monitor should not be reset in FINALIZE type pipeline
Date Thu, 09 Jan 2014 22:35:50 GMT

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

Shi Lu reassigned HELIX-350:
----------------------------

    Assignee: Shi Lu

> 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
>
> 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.1.5#6160)

Mime
View raw message