You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (Updated) (JIRA)" <ji...@apache.org> on 2012/03/08 20:13:57 UTC
[jira] [Updated] (HDFS-3045) fsck move should bail on a file if it
can't create a block file
[ https://issues.apache.org/jira/browse/HDFS-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin Patrick McCabe updated HDFS-3045:
---------------------------------------
Attachment: HDFS-3045.001.patch
* fsck move should bail on a file if it can't create a block file
Note: This is based on the patch I uploaded for HDFS-3044. So perhaps it would be best to review/apply that one first. However, I wanted to put this here before I forgot.
> fsck move should bail on a file if it can't create a block file
> ---------------------------------------------------------------
>
> Key: HDFS-3045
> URL: https://issues.apache.org/jira/browse/HDFS-3045
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Reporter: Eli Collins
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-3045.001.patch
>
>
> NamenodeFsck#lostFoundMove, when it fails to create a file for a block continues on to the next block (There's a comment "perhaps we should bail out here..." but it doesn't). It should instead fail the move for that particular file (unwind the directory creation and not delete the original file). Otherwise a transient failure speaking to the NN means this block is lost forever.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira