[CURATOR-106] Issuing a guaranteed delete can cause stack overflow if ZK is not reachable

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.4.2
• Fix Version/s: awaiting-response
• Component/s: Framework
• Assignee: Unassigned
• Reporter: Jasdeep Hundal
• Created: 08/May/14 22:36
• Updated: 30/May/17 19:45

Description

For guaranteed deletes (eg. lock releases) that fail, the FailedDeleteManager issues another guaranteed delete here:
https://github.com/apache/curator/blob/master/curator-framework/src/main/java/org/apache/curator/framework/imps/FailedDeleteManager.java#L35

In an environment where ZK has the potential to be down for an extended period of time, this has the potential to recurse until there is a stack overflow (particularly if the application is using multiple locks.)

Issue Links

• links to: GitHub Pull Request #215