helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HELIX-681) Participant should not fail state transition on fail to delete / relay message
Date Wed, 25 Apr 2018 01:05:00 GMT

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

ASF GitHub Bot commented on HELIX-681:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/helix/pull/197


> 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)

Mime
View raw message