[
https://issues.apache.org/jira/browse/HADOOP-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527287
]
Hadoop QA commented on HADOOP-1774:
-----------------------------------
-1, build or testing failed
2 attempts failed to build and test the latest attachment
http://issues.apache.org/jira/secure/attachment/12365759/HADOOP-1774-correction.patch
against trunk revision r575438.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/753/testReport/
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/753/console
Please note that this message is automatically generated and may represent a
problem with the automation system and not the patch.
> 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
> Components: dfs
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Fix For: 0.15.0
>
> Attachments: HADOOP-1774-correction.patch, HADOOP-1774.patch,
> HADOOP-1774.patch, 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.
