You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Rodrigo Schmidt (JIRA)" <ji...@apache.org> on 2010/02/19 08:47:28 UTC
[jira] Updated: (MAPREDUCE-1510) RAID should regenerate parity
files if they get deleted
[ 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.patch
This patch should cover this and fix the unit test.
> 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.