[
https://issues.apache.org/jira/browse/HELIX-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451480#comment-16451480
]
Hudson commented on HELIX-681:
------------------------------
FAILURE: Integrated in Jenkins build helix #1461 (See
[https://builds.apache.org/job/helix/1461/])
[HELIX-681] change controller msg purge timeout to larger number (zhan849: rev
ba86a3f554d600a2f781f0975335f3bad431a3ba)
* (edit) helix-core/src/test/java/org/apache/helix/ZkUnitTestBase.java
* (edit)
helix-core/src/main/java/org/apache/helix/controller/stages/MessageGenerationPhase.java
* (edit) helix-core/src/main/java/org/apache/helix/SystemPropertyKeys.java
* (edit)
helix-core/src/test/java/org/apache/helix/controller/stages/TestRebalancePipeline.java
> Participant should not fail state transition on fail to delete / relay message
> ------------------------------------------------------------------------------
>
> Key: HELIX-681
> URL: https://issues.apache.org/jira/browse/HELIX-681
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Hao Zhang
> Priority: Major
>
> Currently we have a general try-catch block in HelixTask and
> HelixTaskExecutor, which, upon any exception thrown from state transition
> routine, will fail state transition. However there are at least the following
> cases in which state transition should be considered as successful:
> * When we fail to delete message after successfully handled message and
> updated current state -> this is because we already completed state
> transition and current state is consistent between participant and ZK
> * When we fail to send out relay message > as relay message provides only
> best effort of delivering messages, which has nothing to do with state
> transition's results. In case of fail to relay message, controller will
> resend message which ensures correctness.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
