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

Hudson commented on HBASE-20857:
--------------------------------

Results for branch branch-1.4
        [build #484 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/484/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/484//General_Nightly_Build_Report/]


(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/484//JDK7_Nightly_Build_Report/]


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




(x) {color:red}-1 source release artifact{color}
-- See build output for details.


> JMX - add Balancer status = enabled / disabled
> ----------------------------------------------
>
>                 Key: HBASE-20857
>                 URL: https://issues.apache.org/jira/browse/HBASE-20857
>             Project: HBase
>          Issue Type: Improvement
>          Components: API, master, metrics, REST, tooling, Usability
>            Reporter: Hari Sekhon
>            Assignee: Kiran Kumar Maturi
>            Priority: Major
>             Fix For: 3.0.0, 1.5.0, 2.2.0, 1.4.8, 2.1.1
>
>         Attachments: HBASE-20857.branch-1.4.001.patch, 
> HBASE-20857.branch-1.4.002.patch
>
>
> Add HBase Balancer enabled/disabled status to JMX API on HMaster.
> Right now the HMaster will give a warning near the top of HMaster UI if 
> balancer is disabled, but scraping this is for monitoring integration is not 
> nice, it should be available in JMX API as there is already a 
> Master,sub=Balancer bean with metrics for the balancer ops etc.



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

Reply via email to