[
https://issues.apache.org/jira/browse/CURATOR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770724#comment-13770724
]
Michael Morello commented on CURATOR-52:
----------------------------------------
I think there is a problem with the way the callback is called in case of
connection loss : in that case the background callback is not actually invoked
"in background" but directly in the same thread.
In case of a recursive call in the callback the thread blow up quickly with a
stack overflow error, here is an example :
https://gist.github.com/barkbay/6607155
btw this is exactly what I want to do in CURATOR-45
> Retry issues with background operations
> ---------------------------------------
>
> Key: CURATOR-52
> URL: https://issues.apache.org/jira/browse/CURATOR-52
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 2.2.0-incubating
> Reporter: Michael Morello
> Assignee: Jordan Zimmerman
> Fix For: 2.3.0-incubating
>
> Attachments: CURATOR-52.patch
>
>
> Retry-able errors (CONNECTIONLOSS, OPERATIONTIMEOUT, SESSIONMOVED,
> SESSIONEXPIRED) are not propagated to callback when the retry policy gave up
> if the operation is done in background.
> Additionally, all background operations do not retry connection issues if the
> zookeeper connection is not currently connected. This is a major oversight.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
