You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/07/11 22:35:06 UTC
[jira] [Commented] (HELIX-453) On session expiry/recovery, not all
message types are re-registered
[ https://issues.apache.org/jira/browse/HELIX-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059315#comment-14059315 ]
Hudson commented on HELIX-453:
------------------------------
FAILURE: Integrated in helix #1258 (See [https://builds.apache.org/job/helix/1258/])
[HELIX-453] On session expiry/recovery, not all message types are re-registered, rb=22432 (kanak: rev 0ee1cdc42d97068924c8d978e68ae78f606d44a5)
* helix-core/src/test/java/org/apache/helix/integration/TestZkSessionExpiry.java
* recipes/jobrunner-yarn/pom.xml
* helix-core/src/main/java/org/apache/helix/messaging/handling/HelixTaskExecutor.java
* recipes/helloworld-provisioning-yarn/pom.xml
> On session expiry/recovery, not all message types are re-registered
> -------------------------------------------------------------------
>
> Key: HELIX-453
> URL: https://issues.apache.org/jira/browse/HELIX-453
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Kanak Biscuitwala
> Assignee: Zhen Zhang
>
> When the session expires, we unregister all message types. When a new session is started, we only add back state transition messages and scheduler task messages. We should be able to add back everything that was registered and not removed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)