helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Nayak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HELIX-514) ZkBaseDataAccessor#set() should throw BadVersionException instead of return false in case of version mismatch
Date Mon, 08 Sep 2014 20:59:28 GMT

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

Sandeep Nayak commented on HELIX-514:
-------------------------------------

Instead of a BadVersionException maybe we need to think about what does the version mismatch
indicate? It appears like its a concurrency issue so maybe we should report an exception to
indicate that an optimistic concurrency exception occurred. Just a thought.

> ZkBaseDataAccessor#set() should throw BadVersionException instead of return false in
case of version mismatch
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HELIX-514
>                 URL: https://issues.apache.org/jira/browse/HELIX-514
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Zhen Zhang
>            Assignee: Zhen Zhang
>
> ZkBaseDataAccessor#set() should throw BadVersionException instead of return false in
case of version mismatch, since caller (e.g. HelixGroupCommit#commit()) may need to distinguish
between fatal error and transient error (e.g. version mismatch) so it can retry.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message