[
https://issues.apache.org/jira/browse/HDFS-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792542#comment-13792542
]
Steve Loughran commented on HDFS-5345:
--------------------------------------
cause is the XmlBlockInfo ctor assumes that if a block ID is passed in, it is
valid
{code}
this.inode = blockManager != null ?
((INode)blockManager.getBlockCollection(block)).asFile() :
null;
{code}
but {{getBlockCollection}} may return null -this needs to be checked for
> NPE in block_info_xml JSP if the block has been deleted
> -------------------------------------------------------
>
> Key: HDFS-5345
> URL: https://issues.apache.org/jira/browse/HDFS-5345
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 2.2.0
> Reporter: Steve Loughran
> Priority: Minor
>
> If you ask for a block info report on a block that has been deleted, you see
> a stack trace and a 500 error.
> Steps to replicae
> # create a file
> # browse to it
> # get the block info
> # delete the file
> # reload the block info page
> Maybe a 404 is the response to raise instead
--
This message was sent by Atlassian JIRA
(v6.1#6144)
