hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5077) NPE in FSNamesystem.commitBlockSynchronization()
Date Thu, 15 Aug 2013 01:01:40 GMT

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

Konstantin Shvachko commented on HDFS-5077:
-------------------------------------------

Yes this is pretty rare, but if I hit it (yes while testing HA), so others could too. The
reason is similar to yours. But whatever the reason we should fix NPE.
                
> NPE in FSNamesystem.commitBlockSynchronization()
> ------------------------------------------------
>
>                 Key: HDFS-5077
>                 URL: https://issues.apache.org/jira/browse/HDFS-5077
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.5-alpha
>            Reporter: Konstantin Shvachko
>
> NN starts a block recovery, which will synchronize block replicas on different DNs. In
the end one of DNs will report the list of the nodes containing the consistent replicas to
the NN via commitBlockSynchronization() call. The NPE happens if just before processing commitBlockSynchronization()
NN removes from active one of DNs that are then reported in the call.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message