curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CURATOR-42) Background guaranteed delete considers NoNode to be a failed delete, and retries it
Date Tue, 24 Sep 2013 01:51:02 GMT

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

Jordan Zimmerman edited comment on CURATOR-42 at 9/24/13 1:49 AM:
------------------------------------------------------------------

I don't see how this can happen. Nodes get added to FailedDeleteManager only for retry-able
exceptions. NoNoException is not retry-able.
                
      was (Author: randgalt):
    I don't see how this can happen. Nodes get added FailedDeleteManager only for retry-able
exceptions. NoNoException is not retry-able.
                  
> 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 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

Mime
View raw message