Github user srdo commented on the issue:
https://github.com/apache/curator/pull/215
@Randgalt I'm probably just going to leave this alone. The stack trace I
posted on the JIRA issue was from an application running 2.12.0. I've been
unable to provoke the stack overflow on 3.x. It still looks like it's possible
for the FailedDeleteManager to recurse a bunch through the same path as in the
stack trace, but since I can't provoke the error I'm not sure the bug still
exists. Since I can't test a potential fix I'd rather not change the code, at
least not unless someone encounters the error on 3.x.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
