hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-3335) check for edit log corruption at the end of the log
Date Fri, 27 Apr 2012 20:20:50 GMT
Colin Patrick McCabe created HDFS-3335:

             Summary: check for edit log corruption at the end of the log
                 Key: HDFS-3335
                 URL: https://issues.apache.org/jira/browse/HDFS-3335
             Project: Hadoop HDFS
          Issue Type: Improvement
    Affects Versions: 0.23.0
            Reporter: Colin Patrick McCabe
            Assignee: Colin Patrick McCabe

Even after encountering an OP_INVALID, we should check the end of the edit log to make sure
that it contains no more edits.

This will catch things like rare race conditions or log corruptions that would otherwise remain
undetected.  They will got from being silent data loss scenarios to being cases that we can
detect and fix.

Using recovery mode, we can choose to ignore the end of the log if necessary.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message