You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "Shi Lu (JIRA)" <ji...@apache.org> on 2013/04/17 20:27:17 UTC
[jira] [Updated] (HELIX-32) Flapping detection: if a helix manager
starts connect/disconnect frequently it should be disconnected
[ https://issues.apache.org/jira/browse/HELIX-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shi Lu updated HELIX-32:
------------------------
Description: Now each helix manager created will remember its connect/disconnect history and if in certain time T, n disconnects has happened it will automatically disconnect from zookeeper. (was: 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.)
Summary: Flapping detection: if a helix manager starts connect/disconnect frequently it should be disconnected (was: collect the zk connects/disconnects every cycle and report it to controller)
> Flapping detection: if a helix manager starts connect/disconnect frequently it should be disconnected
> -----------------------------------------------------------------------------------------------------
>
> 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
>
>
> Now each helix manager created will remember its connect/disconnect history and if in certain time T, n disconnects has happened it will automatically disconnect from zookeeper.
--
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