[
https://issues.apache.org/jira/browse/CURATOR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763399#comment-13763399
]
Jordan Zimmerman commented on CURATOR-52:
-----------------------------------------
This exposes a major oversight. Background operations do not retry connection
failures that occur when calling client.getZooKeeper(). This is a big hole that
I will fix asap.
> Callbacks are not called on retry-able errors
> ---------------------------------------------
>
> 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.2.1-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.
--
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
