[ http://issues.apache.org/jira/browse/HADOOP-803?page=all ]
Raghu Angadi updated HADOOP-803:
--------------------------------
Attachment: block-refs-3.patch
block-refs-3.patch:
1) changed to getBlock(Block) to getBlock( long blockid ). Note that this
version includes a 'new'.
2) Konstantin found a bug because of change in semantics of removeStoredBlock()
and addStoredBlock().
previously they did not modify node's map. restored.
this also slightly modifies Block.compareTo().
Why not have TreeMap<BlockId, Block> instead of TreeMap<Block, Block>?
BlockId is long and it needs to be Long for this generic class. That implies
another allocation of Long for each element in the map.
> Reducing memory consumption on Namenode : Part 1
> ------------------------------------------------
>
> Key: HADOOP-803
> URL: http://issues.apache.org/jira/browse/HADOOP-803
> Project: Hadoop
> Issue Type: Bug
> Reporter: Raghu Angadi
> Assigned To: Raghu Angadi
> Attachments: block-refs-2.patch, block-refs-3.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
