[jira] [Commented] (CURATOR-430) deletingChildrenIfNeeded maybe cannot delete children completely when multi-client delete concurrently

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on CURATOR-430:
----------------------------------------

Github user Randgalt commented on the issue:

    https://github.com/apache/curator/pull/235
  
    @hebelala hey - the test for this PR keeps failing and as I read it, I don't see how it ever worked. Can you look at this again? The code `client2.delete().forPath("/parent/child" + (childCount / 2));` should actually fail most of the time as the thread has deleted all the children.


> deletingChildrenIfNeeded maybe cannot delete children completely when multi-client delete concurrently
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CURATOR-430
>                 URL: https://issues.apache.org/jira/browse/CURATOR-430
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Client
>            Reporter: hebelala
>            Priority: Major
>             Fix For: 4.0.1
>
>
> use curatorFramework.delete().deletingChildrenIfNeeded().forPath(path), this sync api doesn't ignore the NoNodeException, causes the rest of children nodes will not be deleted perhaps.
> zookeeper.getChildren(path, null) maybe throw NoNodeException, if the path doesn't exist.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)