[
https://issues.apache.org/jira/browse/MAPREDUCE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835687#action_12835687
]
Hadoop QA commented on MAPREDUCE-1510:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12436294/MAPREDUCE-1510.patch
against trunk revision 911519.
+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 warnings.
+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 passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/465/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/465/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/465/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/465/console
This message is automatically generated.
> RAID should regenerate parity files if they get deleted
> -------------------------------------------------------
>
> Key: MAPREDUCE-1510
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1510
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/raid
> Reporter: Rodrigo Schmidt
> Assignee: Rodrigo Schmidt
> Attachments: MAPREDUCE-1510.patch
>
>
> Currently, if a source file has a replication factor lower or equal to that
> expected by RAID, the file is skipped and no parity file is generated. I
> don't think this is a good behavior since parity files can get wrongly
> deleted, leaving the source file with a low replication factor. In that case,
> raid should be able to recreate the parity file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
