[
http://issues.apache.org/jira/browse/HADOOP-803?page=comments#action_12458989 ]
Raghu Angadi commented on HADOOP-803:
-------------------------------------
please disregard 4. diff between patch 5 and 3:
- block = containingNodes.first().getBlock(block.getBlockId());
+ Block storedBlock =
+ containingNodes.first().getBlock(block.getBlockId());
+ // update stored block's length.
+ if ( block.getNumBytes() > 0 ) {
+ storedBlock.setNumBytes( block.getNumBytes() );
+ block = storedBlock;
+ }
> Reducing memory consumption on Namenode : Part 1
> ------------------------------------------------
>
> Key: HADOOP-803
> URL: http://issues.apache.org/jira/browse/HADOOP-803
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: Raghu Angadi
> Assigned To: Sameer Paranjpye
> Attachments: block-refs-2.patch, block-refs-3.patch,
> block-refs-5.patch
>
>
> There appears to be some places in Namenode that allow reducing memory
> consumption without intrusive code or feature changes. This bug is an initial
> attempt making those changes. Please include your thoughts as well.
> One change I am planning to make :
> Currently one copy of each block exists for each of the replicas and one copy
> for blockMap. I think they are all supposed to be same.
--
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
