[CURATOR-430] deletingChildrenIfNeeded maybe cannot delete children completely when multi-client delete concurrently

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.1
• Component/s: Client
• Assignee: Unassigned
• Reporter: hebelala
• Created: 12/Aug/17 04:58
• Updated: 09/Dec/18 07:17
• Resolved: 24/Sep/17 20:56

Description

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.

Issue Links

• links to: GitHub Pull Request #235