[ 
https://issues.apache.org/jira/browse/HBASE-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657799#comment-16657799
 ] 

Hudson commented on HBASE-21345:
--------------------------------

Results for branch branch-2.0
        [build #979 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/979/]: 
(x) *{color:red}-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/979//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/979//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/979//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> [hbck2] Allow version check to proceed even though master is 'initializing'.
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-21345
>                 URL: https://issues.apache.org/jira/browse/HBASE-21345
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck2
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.1.1, 2.0.3
>
>         Attachments: 
> 0001-HBASE-21345-hbck2-Allow-version-check-to-proceed-eve.patch, 
> 0001-HBASE-21345-hbck2-Allow-version-check-to-proceed-eve.patch
>
>
> We recently added to hbck2 a check of the cluster version it is to go 
> against. This means a getClusterMetrics call with the option HBASE_VERSION 
> set.
> In testing, trying to fix a failed namespace assign on startup, hbck2 was 
> shut out with a "PleaseHoldException".
> Let the getClusterMetrics call happen even during startup... so tooling can 
> probe Master state externally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to