hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raju (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0
Date Tue, 31 Jul 2012 15:36:34 GMT

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

Raju commented on HDFS-3731:

{quote}We should probably hook the "finalize" code to also rm -rf the "blocksbeingwritten"
directory, or else the storage will be leaked forever, right?{quote}

Yes Todd forget to mention about finalize, we need to delete the BBW dir in finalize

{quote}If you agree, may be we can file separate JIRA for that, as this JIRA mainly talking
about 2.0 upgrade from 1.0.

Uma I accept your opinion but we need to modify the code which is already released, I am not
very clear on how to fix the same.

{quote}I thought that hardlinks to directories are not typically supported ...{quote}
Robert Here I am not directly referring to Hardlink like
ln sourceDir destDir

I am talking about using 
void org.apache.hadoop.hdfs.server.datanode.DataStorage.linkBlocks(File from, File to, int
oldLV, HardLink hl)

which will do the individual file linking for all the blocks.

> 2.0 release upgrade must handle blocks being written from 1.0
> -------------------------------------------------------------
>                 Key: HDFS-3731
>                 URL: https://issues.apache.org/jira/browse/HDFS-3731
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 2.0.0-alpha
>            Reporter: Suresh Srinivas
>            Assignee: Todd Lipcon
>            Priority: Blocker
> Release 2.0 upgrades must handle blocks being written to (bbw) files from 1.0 release.
Problem reported by Brahma Reddy.

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


View raw message