[
https://issues.apache.org/jira/browse/HDFS-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850818#action_12850818
]
Hadoop QA commented on HDFS-1061:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12439929/HDFS-1061.patch
against trunk revision 927999.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause tar ant target to fail.
-1 findbugs. The patch appears to cause Findbugs to fail.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/286/testReport/
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/286/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/286/console
This message is automatically generated.
> Memory footprint optimization for INodeFile object.
> ----------------------------------------------------
>
> Key: HDFS-1061
> URL: https://issues.apache.org/jira/browse/HDFS-1061
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.22.0
> Reporter: Bharath Mundlapudi
> Assignee: Bharath Mundlapudi
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: HDFS-1061.patch
>
>
> I am proposing a footprint optimization to merge blockReplication and
> preferredBlockSize fields into one 'long header' field in INodeFile class.
> This saves 8 bytes per INodeFile object on a 64 bit JVM. This memory
> optimization is transparent and changes are very minimal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
