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

Hudson commented on HBASE-18559:
--------------------------------

Results for branch HBASE-18467, done in 4 hr 24 min and counting
        [build #136 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-18467/136/]: 
FAILURE
----
details (if available):

(x) *{color:red}-1 overall{color}*
    Committer, please check your recent inclusion of a patch for this issue.

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










(/) {color:green}+1 jdk8 checks{color}
-- For more information [see jdk8 
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-18467/136//JDK8_Nightly_Build_Report/]


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



> Add histogram to MetricsConnection to track concurrent calls per server
> -----------------------------------------------------------------------
>
>                 Key: HBASE-18559
>                 URL: https://issues.apache.org/jira/browse/HBASE-18559
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Robert Yokota
>            Assignee: Robert Yokota
>            Priority: Minor
>             Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
>         Attachments: HBASE-18559.master.001.patch
>
>
> HBASE-16388 introduced a new configuration setting 
> "hbase.client.perserver.requests.threshold " to deal with slow region 
> servers.   I have back-ported the code for the new config setting to our 
> environment, but I don't feel comfortable setting it in production without 
> visibility into how the number of concurrent calls per server varies 
> (especially the current high water mark or max in production when the cluster 
> is healthy).  
> It is straightforward to pass the value for the concurrent calls per server 
> to a new histogram in MetricsConnection.  I will attach a patch that I am 
> using to gain a better understanding of how setting 
> "hbase.client.perserver.requests.threshold" will affect our production 
> environment.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to