You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2007/09/01 00:17:18 UTC
[jira] Updated: (HADOOP-1774) Remove use of INode.parent in Block
CRC upgrade
[ https://issues.apache.org/jira/browse/HADOOP-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-1774:
---------------------------------
Attachment: HADOOP-1774.patch
Patch attached. This adds a new class {{INodeWrapper}} inside {{BlockCrcUpgradeObjectNamenode}}. This increase memory required for INode by 40 bytes ( (48 for HashMapEntry + 32 for INodeWrapper) for half the INodes, on 64 bit JVM).
> Remove use of INode.parent in Block CRC upgrade
> -----------------------------------------------
>
> Key: HADOOP-1774
> URL: https://issues.apache.org/jira/browse/HADOOP-1774
> Project: Hadoop
> Issue Type: Improvement
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Fix For: 0.15.0
>
> Attachments: HADOOP-1774.patch
>
>
> HADOOP-1687 proposes various reductions in Namenode memory. One of the 'cuts' is to remove 'parent' field in INodes (8 bytes per file). HADOOP-1743 already deprecates INode.getAbsoluteName() method.
> Block CRC Upgrade code still requires this field (blockID -> fileName -> parent -> INode for .crc file). If we don't want to use parent, we need to build INode-to-parent map at the beginning of the upgrade. Note this would increase memory required during upgrade by 50 bytes for each of non-crc files (50% of files). I would estimate this to be around 5% more memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.