[
https://issues.apache.org/jira/browse/HDFS-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-5279:
--------------------------------
Attachment: HDFS-5279.2.patch
Thanks, [~sureshms]. I'm attaching version 2 of the patch, which sets an
"initializing" label and refactors some duplicated code for generating the
label behind a helper method. Regarding the 0 counts, this was part of the XML
output, and I figured it was safer to emit the exact same XML structure with 0
values, just in case of compatibility problems with anything that parses that
XML and isn't equipped to handle missing elements or new elements.
> 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-5279.2.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)
