hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4872) Idempotent delete operation.
Date Tue, 04 Jun 2013 05:16:20 GMT

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

Suresh Srinivas commented on HDFS-4872:
---------------------------------------

{quote}
Just mark delete idempotent.
A delete retry may delete an object that has been recreated or replaced between the retries
in this case.
{quote}
I am -1 on this.

{quote}
Replace delete with idempotent rename to a temporary object, then delete the latter with non-idempotent
delete.
See the beginning of this comment.
{quote}
Since this requires two requests - one for rename and then delete, the better approach is
to get inode ID and then delete a file using inode ID. delete with unique inode ID is idempotent.

                
> Idempotent delete operation.
> ----------------------------
>
>                 Key: HDFS-4872
>                 URL: https://issues.apache.org/jira/browse/HDFS-4872
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.0.4-alpha
>            Reporter: Konstantin Shvachko
>
> Making delete idempotent is important to provide uninterrupted job execution in case
of HA failover.
> This is to discuss different approaches to idempotent implementation of delete.

--
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