[
https://issues.apache.org/jira/browse/HBASE-20670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501309#comment-16501309
]
Hudson commented on HBASE-20670:
--------------------------------
Results for branch branch-2.0
[build #389 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/389/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/389//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/389//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/389//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> NPE in HMaster#isInMaintenanceMode
> ----------------------------------
>
> Key: HBASE-20670
> URL: https://issues.apache.org/jira/browse/HBASE-20670
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.2
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 3.0.0, 2.1.0, 1.5.0, 2.0.1, 1.4.5
>
> Attachments: HBASE-20670-branch-1.patch, HBASE-20670.patch
>
>
> {noformat}
> Problem accessing /master-status. Reason: INTERNAL_SERVER_ERROR
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.HMaster.isInMaintenanceMode(HMaster.java:2559)
> {noformat}
> The ZK trackers, including the maintenance mode tracker, are initialized only
> after we try to bring up the filesystem. If HDFS is in safe mode and the
> master is waiting on that, when an access to the master status page comes in
> we trip over this problem. There might be other issues after we fix this, but
> NPE Is always a bug, so let's address it. One option is to connect the ZK
> based components with ZK before attempting to bring up the filesystem. Let me
> try that first. If that doesn't work we could at least throw an IOE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
