hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nkeywal (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-6401) HBase may lose edits after a crash if used with HDFS 1.0.3 or older
Date Tue, 17 Jul 2012 12:36:34 GMT
nkeywal created HBASE-6401:

             Summary: HBase may lose edits after a crash if used with HDFS 1.0.3 or older
                 Key: HBASE-6401
                 URL: https://issues.apache.org/jira/browse/HBASE-6401
             Project: HBase
          Issue Type: Bug
          Components: regionserver
    Affects Versions: 0.96.0
         Environment: all
            Reporter: nkeywal
            Priority: Critical

This comes from a hdfs bug, fixed in some hdfs versions. I haven't found the hdfs jira for

Context: HBase Write Ahead Log features. This is using hdfs append. If the node crashes, the
file that was written is read by other processes to replay the action.
- So we have in hdfs one (dead) process writing with another process reading.
- But, despite the call to syncFs, we don't always see the data when we have a dead node.
It seems to be because the call in DFSClient#updateBlockInfo ignores the ipc errors and set
the length to 0.
- So we may miss all the writes to the last block if we try to connect to the dead DN.

hdfs 1.0.3, branch-1 or branch-1-win: we have the issue

hdfs branch-2 or trunk: we should not have the issue (but not tested)

The attached test will fail ~50 of the time.

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