hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-140) When a file is deleted, its blocks remain in the blocksmap till the next block report from Datanode
Date Wed, 12 Oct 2011 06:11:11 GMT

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

Todd Lipcon commented on HDFS-140:
----------------------------------

Hi Uma. Is this already resolved in trunk? Having trouble following the various JIRAs (many
seem to be resolved as dup). Which JIRA fixed it in trunk, and what's the motivation to fix
in the maintenance release?

I haven't looked at the patch yet, but seems like a potentially destabilizing change to introduce
if there aren't any burning issues that are caused by the lack of this improvement.
                
> When a file is deleted, its blocks remain in the blocksmap till the next block report
from Datanode
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-140
>                 URL: https://issues.apache.org/jira/browse/HDFS-140
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.20.1
>            Reporter: dhruba borthakur
>            Assignee: Uma Maheswara Rao G
>             Fix For: 0.20.205.0
>
>         Attachments: HDFS-140.20security205.patch
>
>
> When a file is deleted, the namenode sends out block deletions messages to the appropriate
datanodes. However, the namenode does not delete these blocks from the blocksmap. Instead,
the processing of the next block report from the datanode causes these blocks to get removed
from the blocksmap.
> If we desire to make block report processing less frequent, this issue needs to be addressed.
Also, this introduces indeterministic behaviout to a a few unit tests. Another factor to consider
is to ensure that duplicate block detection is not compromised.

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

        

Mime
View raw message