[
https://issues.apache.org/jira/browse/BOOKKEEPER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108761#comment-13108761
]
Flavio Junqueira commented on BOOKKEEPER-68:
--------------------------------------------
I think you're right in that we would need such an external mechanism anyway
because the absence of a failure does not imply that it is ok to take over in
my example. Consequently, retrying does not make it more difficult for the
application.
I still feel that the code is simpler without retrying, though, and it doesn't
sound like a big deal for the application to retry if it needs to. At the same
time, I'm possibly not the best person to ask about APIs, so I'm willing to
change my mind here if there is a good reason for doing it.
> Conditional setData
> -------------------
>
> Key: BOOKKEEPER-68
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-68
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Flavio Junqueira
> Assignee: Flavio Junqueira
> Attachments: BOOKKEEPER-68.patch
>
>
> The write to ZooKeeper to store ledger metadata when closing a ledger must be
> conditional, otherwise concurrent clients might end up writing in a way that
> the update of a client overwrites the update of the other.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
