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

Hudson commented on HELIX-681:
------------------------------

FAILURE: Integrated in Jenkins build helix #1422 (See 
[https://builds.apache.org/job/helix/1422/])
[HELIX-681] don't fail state transition task if we fail to remove (zhan849: rev 
c1ab0b5ed27c777ef63bfc7247415b6928e72906)
* (edit) helix-core/src/main/java/org/apache/helix/util/HelixUtil.java
* (edit) 
helix-core/src/main/java/org/apache/helix/messaging/handling/HelixTask.java
* (edit) 
helix-core/src/main/java/org/apache/helix/messaging/handling/HelixTaskExecutor.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)

Reply via email to