You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/10 04:00:48 UTC
[jira] [Updated] (HDFS-1982) Null pointer exception is thrown when
NN restarts with a block lesser in size than the block that is present in
DN1 but the generation stamp is greater in the NN
[ https://issues.apache.org/jira/browse/HDFS-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HDFS-1982:
-----------------------------------
Fix Version/s: (was: 0.20-append)
> Null pointer exception is thrown when NN restarts with a block lesser in size than the block that is present in DN1 but the generation stamp is greater in the NN
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-1982
> URL: https://issues.apache.org/jira/browse/HDFS-1982
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.20-append
> Environment: Linux
> Reporter: ramkrishna.s.vasudevan
>
> Conisder the following scenario.
> WE have a cluster with one NN and 2 DN.
> We write some file.
> One of the block is written in DN1 but not yet completed in DN2 local disk.
> Now DN1 gets killed and so pipeline recovery happens for the block with the size as in DN2 but the generation stamp gets updated in the NN.
> DN2 also gets killed.
> Now restart NN and DN1
> Now if NN restarts, the block that NN has greater time stamp but the size is lesser in the NN.
> This leads to Null pointer exception in addstoredblock api
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)