[
https://issues.apache.org/jira/browse/BOOKKEEPER-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713817#comment-13713817
]
Rakesh R commented on BOOKKEEPER-649:
-------------------------------------
Hi,
There is a logic in ZkLedgerUnderreplicationManager.java, where
#markLedgerUnderreplicated() is handling KeeperException.NodeExistsException.
Once received KeeperException.NodeExistsException, its having special logic to
mark the 'missingReplica' details in the ledger node path. The test case
failure is due to this and could not fully suppress the NodeExistsException.
> 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.3.0
>
> Attachments:
> 0001-BOOKKEEPER-649-Race-condition-in-sync-ZKUtils.create.patch,
> 0002-BOOKKEEPER-649.patch, 0002-BOOKKEEPER-649.patch
>
>
> 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
