You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/04/02 18:47:00 UTC

[jira] [Updated] (HBASE-26891) Make MetricsConnection scope configurable

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

Andrew Kyle Purtell updated HBASE-26891:
----------------------------------------
    Fix Version/s: 2.5.0
                   3.0.0-alpha-3

> Make MetricsConnection scope configurable
> -----------------------------------------
>
>                 Key: HBASE-26891
>                 URL: https://issues.apache.org/jira/browse/HBASE-26891
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Bryan Beaudreault
>            Assignee: Bryan Beaudreault
>            Priority: Minor
>              Labels: patch-available
>             Fix For: 2.5.0, 3.0.0-alpha-3
>
>
> Currently MetricsConnection scope is just the connection.toString(), which is typically the default toString() implementation for an object. This is not very useful for identifying different connections in processes that might connect to multiple clusters or maintain different connections to the same cluster.
> We can add a new config param "hbase.client.metrics.scope" which defaults to connection.toString().



--
This message was sent by Atlassian Jira
(v8.20.1#820001)