hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Kling (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-2156) Raid-aware FSCK
Date Tue, 30 Nov 2010 22:34:13 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Patrick Kling updated MAPREDUCE-2156:

    Attachment: MAPREDUCE-2156.patch

See review board: https://reviews.apache.org/r/132/

ant test-patch output:

     [exec] +1 overall.  
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     +1 tests included.  The patch appears to include 4 new or modified tests.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9)
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.
     [exec]     +1 system test framework.  The patch passed system test framework compile.

> Raid-aware FSCK
> ---------------
>                 Key: MAPREDUCE-2156
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2156
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: contrib/raid
>    Affects Versions: 0.23.0
>            Reporter: Patrick Kling
>             Fix For: 0.23.0
>         Attachments: MAPREDUCE-2156.patch
> Currently, FSCK reports files as corrupt even if they can be fixed using parity blocks.
We need a tool that only reports files that are irreparably corrupt (i.e., files for which
too many data or parity blocks belonging to the same stripe have been lost or corrupted).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message