Github user srdo commented on the issue:
https://github.com/apache/curator/pull/215
Too bad. Thanks for explaining though. Would you be more in favor of this
patch if I added a new `processBackgroundOperation` instead of modifying the
existing one? The stack overflow error mentioned in CURATOR-106 is happening
because the FailedDeleteManager is assuming that the backgrounded delete
actually happens in the background. When it doesn't, the stack may overflow
because FailedDeleteManager triggers a delete, which may fail, which causes a
call to FailedDeleteManager etc. It likely doesn't happen when retries are
enabled, because only the first try happens in the foreground.
---
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.
---
