[
https://issues.apache.org/jira/browse/MAPREDUCE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839921#action_12839921
]
Rodrigo Schmidt commented on MAPREDUCE-1510:
--------------------------------------------
Hudson is taking too long to generate a report on this one, so I'm doing the
testing myself.
ant test-patch returned the following:
[exec] There appear to be 0 release audit warnings before the patch and 0
release audit warnings after applying the patch.
[exec]
[exec]
[exec]
[exec]
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 12 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec]
[exec]
[exec]
[exec]
======================================================================
[exec]
======================================================================
[exec] Finished build.
[exec]
======================================================================
[exec]
======================================================================
Now I'm running the unit tests
> 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.1.patch, MAPREDUCE-1510.2.patch,
> 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.
