[
https://issues.apache.org/jira/browse/HADOOP-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719719#action_12719719
]
Raghu Angadi commented on HADOOP-5724:
--------------------------------------
Couple of comments:
* To enforce the new policy, it is probably better to call removeBlockFromMap()
from removeINode().
* Or may be we don't need both?
* depending what we do with removeINode(), it may not be necessary to change
removeBlockFromMap(). The new implementation does a look up but does not check
if 'info' is null.
> 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.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.
