You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@helix.apache.org by "dafu (JIRA)" <ji...@apache.org> on 2013/06/21 23:00:20 UTC
[jira] [Commented] (HELIX-134) refactor helix manager to handle zk
session expiry more reliably
[ https://issues.apache.org/jira/browse/HELIX-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690716#comment-13690716 ]
dafu commented on HELIX-134:
----------------------------
https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git
> refactor helix manager to handle zk session expiry more reliably
> ----------------------------------------------------------------
>
> Key: HELIX-134
> URL: https://issues.apache.org/jira/browse/HELIX-134
> Project: Apache Helix
> Issue Type: Bug
> Reporter: dafu
> Assignee: dafu
>
> tasks include:
> 1) separate HelixManager impl for participant, controller, and distributed controller
> 2) take care of consecutive handleNewSession() and session expiry during handleNewSession()
> 3) fix HelixManager#isLeader() bug by comparing both instanceName and sessionId
> 4) wait on all left-over tasks to be cancelled successfully before start new session
--
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