[
https://issues.apache.org/jira/browse/BOOKKEEPER-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747461#comment-13747461
]
Ivan Kelly commented on BOOKKEEPER-649:
---------------------------------------
{quote}
The patch you provide replaces calls to the sync version with calls to the
async version
{quote}
Nope, it renames the async version, so that it's obvious that it is async. The
places it looks like i've replaced sync with async were already async.
Functionalitywise, the only change is in ZKUtils.
> Race condition in sync ZKUtils.createFullPathOptimistic()
> ---------------------------------------------------------
>
> Key: BOOKKEEPER-649
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-649
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Matteo Merli
> Assignee: Matteo Merli
> Priority: Trivial
> Fix For: 4.2.2, 4.3.0
>
> Attachments:
> 0001-BOOKKEEPER-649-Race-condition-in-sync-ZKUtils.create.patch,
> 0001-BOOKKEEPER-649-Race-condition-in-sync-ZKUtils.create.patch,
> 0002-BOOKKEEPER-649.patch, 0002-BOOKKEEPER-649.patch,
> TEST-org.apache.bookkeeper.replication.TestLedgerUnderreplicationManager.xml
>
>
> If multiple threads are calling createFullPathOptimistic() there will be race
> conditions on creating the intermediate nodes. If the intermediate nodes have
> been created since we last check, we can just ignore the exception and
> continue creating the child nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
