curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shevek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-42) DeleteBuilder considers NoNode to be a failed delete
Date Wed, 26 Jun 2013 00:14:21 GMT

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

Shevek commented on CURATOR-42:
-------------------------------

Ah, I misreported the ticket.

It's a background guaranteed-delete, so it's not like the failure is reported to the user
anyway. All that's happening is the background loop is unnecessarily trying to go around and
around and delete a node it KNOWS doesn't exist.
                
> DeleteBuilder considers NoNode to be a failed delete
> ----------------------------------------------------
>
>                 Key: CURATOR-42
>                 URL: https://issues.apache.org/jira/browse/CURATOR-42
>             Project: Apache Curator
>          Issue Type: Bug
>            Reporter: Shevek
>            Assignee: Jordan Zimmerman
>
> 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