hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Mankude (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4872) Idempotent delete operation.
Date Wed, 05 Jun 2013 13:44:21 GMT

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

Hari Mankude commented on HDFS-4872:

modTime cannot be used as unique parameter due to race between delete and append. 

If hdfs had cTime, it would have been a unique file specific value in combination with file
> 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

View raw message