hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (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 Thu, 13 Oct 2011 00:57:11 GMT

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

Uma Maheswara Rao G commented on HDFS-140:
------------------------------------------

Hi,

 I can see only the below problems
 1) memory consumption in NN (if we have many deletes and creates).
 2) block information in UI will not be reflected immediately. But it is not very serious
problems.

 If we have confidence, then only we can push this :-). But in our internal branch we have
fixed it in 6months back (i remember). I don't see any problems with this fix so far.

Thanks a lot for your time to check this issue.

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