[
https://issues.apache.org/jira/browse/HDFS-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018470#comment-13018470
]
Hadoop QA commented on HDFS-1630:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12476020/editsChecksum2.patch
against trunk revision 1090357.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these core unit tests:
org.apache.hadoop.hdfs.TestFileCreationEmpty
-1 contrib tests. The patch failed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/339//testReport/
Findbugs warnings:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/339//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/339//console
This message is automatically generated.
> Checksum fsedits
> ----------------
>
> Key: HDFS-1630
> URL: https://issues.apache.org/jira/browse/HDFS-1630
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.23.0
>
> Attachments: editsChecksum.patch, editsChecksum1.patch,
> editsChecksum2.patch
>
>
> HDFS-903 calculates a MD5 checksum to a saved image, so that we could verify
> the integrity of the image at the loading time.
> The other half of the story is how to verify fsedits. Similarly we could use
> the checksum approach. But since a fsedit file is growing constantly, a
> checksum per file does not work. I am thinking to add a checksum per
> transaction. Is it doable or too expensive?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
