[
https://issues.apache.org/jira/browse/CURATOR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman updated CURATOR-52:
------------------------------------
Description:
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.
was: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.
> 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.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.
> 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
