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

Hudson commented on HBASE-20396:
--------------------------------

Results for branch master
        [build #391 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/391/]: (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/master/391//General_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/master/391//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/master/391//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


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


> Remove redundant MBean from thrift JMX
> --------------------------------------
>
>                 Key: HBASE-20396
>                 URL: https://issues.apache.org/jira/browse/HBASE-20396
>             Project: HBase
>          Issue Type: Improvement
>          Components: Thrift
>            Reporter: Guangxu Cheng
>            Assignee: Guangxu Cheng
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0
>
>         Attachments: HBASE-20396.master.001.patch
>
>
> HBase has two types of thrift server. When any type of thrift server is 
> started, the MBean of the two thrift servers will be registered which is 
> redundant.
> For example, when starting thrift2, we only need to register MBean 
> "Hadoop:service=HBase,name=Thrift,sub=ThriftTwo" of thrift2 in JMX, there's 
> no need to register MBean "Hadoop:service=HBase,name=Thrift,sub=ThriftOne" of 
> thrift. Vice versa



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

Reply via email to