curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-42) Background guaranteed delete considers NoNode to be a failed delete, and retries it
Date Tue, 29 Jul 2014 06:52:39 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077447#comment-14077447
] 

Cameron McKenzie commented on CURATOR-42:
-----------------------------------------

Just had a look at this, the delete definitely gets retried even though the node doesn't exist.
But it only gets retried once. This is because the retry is called with inBackground() with
no callback, so the failure no the retry never gets propagated to the code that does another
retry.

I will fix it so that it doesn't do the initial retry, as it's unnecessary.

> Background guaranteed delete considers NoNode to be a failed delete, and retries it
> -----------------------------------------------------------------------------------
>
>                 Key: CURATOR-42
>                 URL: https://issues.apache.org/jira/browse/CURATOR-42
>             Project: Apache Curator
>          Issue Type: Bug
>            Reporter: Shevek
>            Assignee: Jordan Zimmerman
>             Fix For: awaiting-response
>
>
> In delete(), NoNode should be a special case which succeeds instantly, and does not consider
the delete failed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message