hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5724) Datanode should report deletion of blocks to Namenode explicitly
Date Tue, 16 Jun 2009 22:24:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720383#action_12720383
] 

Suresh Srinivas commented on HADOOP-5724:
-----------------------------------------

I also ran the following manual test:
# Setup HDFS with a long block replication timeout {{dfs.blockreport.intervalMsec}}
# Create a bunch of files in multiple directories
# Delete one directory at a time and ensure on the NameNode web UI, the block count in Cluster
Summary decreases

> Datanode should report deletion of blocks to Namenode explicitly
> ----------------------------------------------------------------
>
>                 Key: HADOOP-5724
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5724
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.21.0
>
>         Attachments: blockdel-1.patch, blockdel-2.patch, blockdel.patch, blockdel.patch
>
>
> Currently datanode notifies namenode newly added blocks and the blocks that are corrupt.
There is no explicit message from the datanode to the namenode to indicate the deletion of
blocks. Block reports from the datanode is the only way for the namenode to learn about the
deletion of blocks at a datanode. With the addition of explicit request to indicate to block
deletion, block report interval (which is currently 1 hour) can be increased to a longer duration.
This reduces load on both namenode and datanodes.
>  

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


Mime
View raw message