[
https://issues.apache.org/jira/browse/HDFS-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782247#comment-13782247
]
Hadoop QA commented on HDFS-5279:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12605950/HDFS-5279.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/5066//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5066//console
This message is automatically generated.
> 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)
