[
https://issues.apache.org/jira/browse/MAPREDUCE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rodrigo Schmidt updated MAPREDUCE-1510:
---------------------------------------
Attachment: MAPREDUCE-1510.2.patch
In an offline discussion, Dhruba made me realize that the fact that the
RaidNode binds to a fixed port is probably the reason why the tests were
failing on Hudson. I'm submitting this new patch that also changes the unit
tests so that now they bind to any available port.
> 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.
