You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Rodrigo Schmidt (JIRA)" <ji...@apache.org> on 2010/04/15 10:24:50 UTC
[jira] Created: (MAPREDUCE-1704) Parity files that are outdated or
nonexistent should be immediately disregarded
Parity files that are outdated or nonexistent should be immediately disregarded
-------------------------------------------------------------------------------
Key: MAPREDUCE-1704
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1704
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/raid
Affects Versions: 0.22.0
Reporter: Rodrigo Schmidt
Assignee: Rodrigo Schmidt
Fix For: 0.22.0
In the current implementation, old or nonexistent parity files are not immediately disregarded. Absence will trigger exceptions, but old files could lead to bad recoveries and maybe data corruption. This should be fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MAPREDUCE-1704) Parity files that are outdated or
nonexistent should be immediately disregarded
Posted by "Scott Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Chen resolved MAPREDUCE-1704.
-----------------------------------
Resolution: Invalid
It's already been fixed.
> Parity files that are outdated or nonexistent should be immediately disregarded
> -------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1704
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1704
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/raid
> Affects Versions: 0.22.0
> Reporter: Rodrigo Schmidt
> Assignee: Scott Chen
> Fix For: 0.22.0
>
>
> In the current implementation, old or nonexistent parity files are not immediately disregarded. Absence will trigger exceptions, but old files could lead to bad recoveries and maybe data corruption. This should be fixed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.