[jira] [Commented] (HELIX-134) refactor helix manager to handle zk session expiry more reliably

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on HELIX-134:
------------------------------

SUCCESS: Integrated in helix #1088 (See [https://builds.apache.org/job/helix/1088/])
HELIX-134: refactor helix manager to handle zk session expiry more reliably. add more tests for new cluster manager impl (zzhang: rev 5d39241061b5c5207cb0bc4177e1a8f725c598f8)
* helix-core/src/test/java/org/apache/helix/integration/manager/MockParticipantManager.java
* helix-core/src/test/java/org/apache/helix/integration/manager/ClusterControllerManager.java
* helix-core/src/test/java/org/apache/helix/integration/manager/TestZkCallbackHandlerLeak.java
* helix-core/src/test/java/org/apache/helix/integration/manager/ZkTestManager.java
* helix-core/src/test/java/org/apache/helix/integration/manager/TestAbstractManager.java

                
> 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