[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837611#action_12837611
 ] 

Rodrigo Schmidt commented on MAPREDUCE-1510:
--------------------------------------------

I really don't know what is going on with Hudson.

It is failing a MiniMR test that is completely unrelated to this patch, but it 
doesn't fail any unit test.

The logs say it is failing contrib unit tests because some services are trying 
to bind to used ports, but it looks like a problem with Hudson more than a 
problem with my patch.

I did a full ant test-patch, followed by an ant test, followed by an ant 
test-contrib, and the only thing that failed was the unrelated MiniMR test.

I'm quite conviced this patch is harmless to trunk. Here is the final part of 
the output from my "ant test-contrib" execution"

...
PASSED ALL PREVIOUS CONTRIB TESTS
...
test-junit:
    [junit] Running org.apache.hadoop.hdfs.TestRaidDfs
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.377 sec
    [junit] Running org.apache.hadoop.raid.TestRaidHar
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 45.107 sec
    [junit] Running org.apache.hadoop.raid.TestRaidNode
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 61.432 sec
    [junit] Running org.apache.hadoop.raid.TestRaidPurge
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 23.123 sec

test:

BUILD SUCCESSFUL


> 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.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.

Reply via email to