hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-18559) Add histogram to MetricsConnection to track concurrent calls per server
Date Sat, 30 Sep 2017 00:13:01 GMT

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

Andrew Purtell resolved HBASE-18559.
      Resolution: Fixed
    Hadoop Flags: Reviewed

Pushed to 1.4 and up

> 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

View raw message