hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5077) NPE in FSNamesystem.commitBlockSynchronization()
Date Mon, 12 Aug 2013 09:35:53 GMT

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

Vinay commented on HDFS-5077:
-----------------------------

Rare to occur, If the removed DN have responded successfully during recovery, then definitely
some problem at DN side in reporting to active NN.
One possible problem in case of HA is HDFS-5014
                
> 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