You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/15 08:05:00 UTC

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

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

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

Github user JunjianS commented on the issue:

    https://github.com/apache/curator/pull/235
  
    i met the same problem, could u please provide a fixed version ?


> 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
>
> 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
(v6.4.14#64029)