You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by Evaristo José Camarero <ev...@yahoo.es> on 2013/09/23 17:03:42 UTC
CURATOR-53 IS CLOSED BUT SOLUTION INTRODUCES A NEW ISSUE
Hi there,
I was testing CURATOR-53 fix, and the solution is introducing a new problem. All the details are included in
https://issues.apache.org/jira/browse/CURATOR-53
Is it needed to open a new JIRA? Is it better to open again the CURATOR-53 issue?
Cheers,
Evaristo
________________________________
De: Michael Morello (JIRA) <ji...@apache.org>
Para: dev@curator.incubator.apache.org
Enviado: Lunes 23 de septiembre de 2013 15:52
Asunto: [jira] [Commented] (CURATOR-52) Retry issues with background operations
[ https://issues.apache.org/jira/browse/CURATOR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774552#comment-13774552 ]
Michael Morello commented on CURATOR-52:
----------------------------------------
Looks good to me, I will update CURATOR-45 asap
> 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
>
> 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