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

Hudson commented on HBASE-20740:
--------------------------------

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


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


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


> StochasticLoadBalancer should consider CoprocessorService request factor when 
> computing cost
> --------------------------------------------------------------------------------------------
>
>                 Key: HBASE-20740
>                 URL: https://issues.apache.org/jira/browse/HBASE-20740
>             Project: HBase
>          Issue Type: Improvement
>          Components: Balancer
>            Reporter: chenxu
>            Assignee: chenxu
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: 20740-master-v2.patch, HBASE-20740-master-v1.patch, 
> HBASE-20740-master-v3.patch
>
>
> When compute region load cost, ReadRequest, WriteRequest, MemStoreSize and 
> StoreFileSize are considered, But CoprocessorService requests are ignored. In 
> our KYLIN cluster, there only have CoprocessorService requests, and the 
> cluster sometimes unbalanced.



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

Reply via email to