hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1510) RAID should regenerate parity files if they get deleted
Date Fri, 19 Feb 2010 08:23:28 GMT

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

dhruba borthakur commented on MAPREDUCE-1510:
---------------------------------------------

code changes look good. is there a test case where the source file is already at the replication
level that is expected post replication bu the modtime of the parity file does not match the
modtime of the src file? In that case, the src file should be re-raided, isn't it?

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


Mime
View raw message