[
https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman updated CURATOR-72:
------------------------------------
Fix Version/s: (was: 2.3.0)
2.3.1
> Background operations don't wait for connection timeout
> -------------------------------------------------------
>
> Key: CURATOR-72
> URL: https://issues.apache.org/jira/browse/CURATOR-72
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 2.3.0
> Reporter: Evaristo Camarero
> Assignee: Jordan Zimmerman
> Fix For: 2.3.1
>
> Attachments: test.java
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
