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 "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2013/09/30 21:26:24 UTC
[jira] [Commented] (HDFS-5279) Guard against NullPointerException
in NameNode JSP pages before initialization of FSNamesystem.
[ https://issues.apache.org/jira/browse/HDFS-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782122#comment-13782122 ]
Suresh Srinivas commented on HDFS-5279:
---------------------------------------
[~cnauroth], how about making a change in the web UI to say "NameNode is initializing" instead of giving either empty string or 0 as count when FSNamesystem is null?
> Guard against NullPointerException in NameNode JSP pages before initialization of FSNamesystem.
> -----------------------------------------------------------------------------------------------
>
> Key: HDFS-5279
> URL: https://issues.apache.org/jira/browse/HDFS-5279
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0, 2.1.1-beta
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-5279.1.patch
>
>
> HDFS-4372 added tracking of NameNode startup progress. As part of that change, the NameNode HTTP server now starts before initialization of the {{FSNamesystem}}. There are a few code paths remaining in the JSP pages that are at risk of causing {{NullPointerException}} if accessed when the {{FSNamesystem}} has not been fully initialized.
--
This message was sent by Atlassian JIRA
(v6.1#6144)