GitHub user hebelala opened a pull request:
https://github.com/apache/curator/pull/235
deletingChildrenIfNeeded maybe cannot delete children completely when
multi-client delete concurrently
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hebelala/curator CURATOR-430
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/235.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #235
----
commit ca1e9fbbb28a9deaa7f6187f321fd446f471db6d
Author: hebelala <hebel...@qq.com>
Date: 2017-08-11T10:39:21Z
Fix, maybe cannot deleteChildren completely when multi-client delete
concurrently
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
