[ 
https://issues.apache.org/jira/browse/HDFS-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970222#comment-13970222
 ] 

Lohit Vijayarenu commented on HDFS-6248:
----------------------------------------

Looking at FSEditLogLoader::applyEditLogOp

{code}
        // add to the file tree
        newFile = (INodeFile)fsDir.unprotectedAddFile(
            addCloseOp.path, addCloseOp.permissions,
            replication, addCloseOp.mtime,
            addCloseOp.atime, addCloseOp.blockSize,
            true, addCloseOp.clientName, addCloseOp.clientMachine);
        fsNamesys.leaseManager.addLease(addCloseOp.clientName, addCloseOp.path);
{code}
could return newFile as null because of QuotaExceededExcetion in 
uprotectedAddFile

NPE exception happens further down in same function at

{code}
     // Update the salient file attributes.
      newFile.setAccessTime(addCloseOp.atime);
      newFile.setModificationTimeForce(addCloseOp.mtime);
      updateBlocks(fsDir, addCloseOp, newFile);
{code}

Even though stack trace points to line number of 2.0.6 release, I could not 
find any changes in trunk source code.

> SNN crash during replay of FSEditLog of files inside directories having 
> QuotaExceeded directories 
> --------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-6248
>                 URL: https://issues.apache.org/jira/browse/HDFS-6248
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.6-alpha, 2.4.0
>         Environment: NameNode HA setup with Active/Standby using QJM
>            Reporter: Lohit Vijayarenu
>
> We are seeing cases when Secondary NameNode crashes without recovery when it 
> tries to replay edit log of files which are part of directories which have 
> exceeded Quota. While debugging we got stack trace but we are still trying to 
> reproduce this and wanted to note this to see if anyone else had seen this 
> issue already. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to