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

Hudson commented on HBASE-24518:
--------------------------------

Results for branch branch-2
        [build #2709 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2709/]: 
(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/2709/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2709/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console 
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2709//console].


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2709/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


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


(/) {color:green}+1 client integration test{color}


> waitForNamespaceOnline() should return false if any region is offline
> ---------------------------------------------------------------------
>
>                 Key: HBASE-24518
>                 URL: https://issues.apache.org/jira/browse/HBASE-24518
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> HMaster waits for namespace regions to come online only for rolling upgrade 
> scenario (from 1.x to 2.x), however, waitForNamespaceOnline() does not return 
> false for any offline region. We should fix this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to