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] [Commented] (HELIX-32) collect the zk connects/disconnects every cycle and report it to controller
Date Wed, 20 Mar 2013 04:23:16 GMT

    [ https://issues.apache.org/jira/browse/HELIX-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607266#comment-13607266
] 

Shi Lu commented on HELIX-32:
-----------------------------

This feature is covered by the flapping detection logic done on the ZkHelixManager side. The
helix manager will dis connect itself if flapping is detected; All helix managers (participant,
controller, spectator) have this capabiliy. Thus we don't need the controller into picture.

                
> collect the zk connects/disconnects every cycle and report it to controller
> ---------------------------------------------------------------------------
>
>                 Key: HELIX-32
>                 URL: https://issues.apache.org/jira/browse/HELIX-32
>             Project: Apache Helix
>          Issue Type: Improvement
>    Affects Versions: 0.6.0-incubating
>            Reporter: kishore gopalakrishna
>            Assignee: Shi Lu
>             Fix For: 0.6.1-incubating
>
>
> Helix agent must collect the zk connects/disconnects and use the health check framework
to convey the information. Controller must disable the nodes are connecting/disconnecting
frequently.

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