hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hong Tang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-677) Rename failure due to quota results in deletion of src directory
Date Thu, 08 Oct 2009 23:04:31 GMT

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

Hong Tang commented on HDFS-677:

bq. 2. During rename after the src is removed, any failure to complete rename is handled by
adding src back without checking for quota.
What kind of failures might we encounter during the rename? How can we guarantee to have no
failures adding src back?

In general, you are trying to make the move operation atomic (either done successfully, or
no effect is happening). This typically means that you want  to prepare as much change on
the side as possible (without changing the state), and effect the state change in one atomic

> Rename failure due to quota results in deletion of src directory
> ----------------------------------------------------------------
>                 Key: HDFS-677
>                 URL: https://issues.apache.org/jira/browse/HDFS-677
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.20.1, 0.20.2, 0.21.0, 0.22.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 0.20.2, 0.21.0, 0.22.0
>         Attachments: hdfs-677.8.patch
> Renaming src to destination where src has exceeded the quota to a dst without sufficent
quota fails. During this failure, src is deleted. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message