hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-6527) Edit log corruption due to defered INode removal
Date Fri, 13 Jun 2014 13:48:01 GMT
Kihwal Lee created HDFS-6527:

             Summary: Edit log corruption due to defered INode removal
                 Key: HDFS-6527
                 URL: https://issues.apache.org/jira/browse/HDFS-6527
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 2.4.0
            Reporter: Kihwal Lee
            Priority: Blocker

We have seen a SBN crashing with the following error:
\[Edit log tailer\] ERROR namenode.FSEditLogLoader:
Encountered exception on operation AddBlockOp
penultimateBlock=NULL, lastBlock=blk_111_111, RpcClientId=,
java.io.FileNotFoundException: File does not exist: /xxx

This was caused by the deferred removal of deleted inodes from the inode map. Since startFile()
acquires FSN read lock and then write lock, a deletion can happen in between. Because of deferred
inode removal outside FSN write lock, startFile() can get the deleted inode from the inode
map with FSN write lock held. This allow addition of a block to a deleted file.

As a result, the edit log will contain OP_ADD, OP_DELETE, followed by
 OP_ADD_BLOCK.  This cannot be replayed by NN, so NN doesn't start up or SBN crashes.

This message was sent by Atlassian JIRA

View raw message