[
https://issues.apache.org/jira/browse/BOOKKEEPER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108627#comment-13108627
]
Flavio Junqueira commented on BOOKKEEPER-68:
--------------------------------------------
I'd rather leave to the application to decide because of the following
argument. Suppose that two clients try to recover the ledger because are on the
way of taking over the role of primary. The fact that one attempt to open the
ledger and recover fails indicates that there has a been a concurrent attempt,
and in this case I would say that the client that gets a failed request should
actually back off.
Does it make sense to you, Ivan?
> 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
