hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-764) The memory consumption of processReport() in the namenode can be reduced
Date Thu, 07 Dec 2006 13:55:26 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-764?page=comments#action_12456417 ] 
dhruba borthakur commented on HADOOP-764:

All those other places you mention actually contain references to the same block object. The
block object is created when the blockReport RPC arrives at the namenode, and then references
to it are stored in Namenode.blockMap as well as DatanodeDescriptor.blocks.

> The memory consumption of processReport() in the namenode can be reduced
> ------------------------------------------------------------------------
>                 Key: HADOOP-764
>                 URL: http://issues.apache.org/jira/browse/HADOOP-764
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>         Assigned To: dhruba borthakur
>         Attachments: processBlockReport3.patch
> The FSNamesystem.processReport() method converts the blocklist for a datanode into an
array by calling node.getBlocks(). Although this memory allocation is transient, it could
possibly require the garbage-collector to work that much harder. 
> The method Block.getBlocks() should be deprecated. Code that currently uses this method
should instead iterate over the Collection.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message