[ 
https://issues.apache.org/jira/browse/HBASE-18559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Yokota updated HBASE-18559:
----------------------------------
    Attachment: HBASE-18559.master.001.patch

> Provide metrics for concurrent calls per server to be able to effectively use 
> new config setting from HBASE-16388
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18559
>                 URL: https://issues.apache.org/jira/browse/HBASE-18559
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Robert Yokota
>            Priority: Minor
>         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