[
https://issues.apache.org/jira/browse/HBASE-26891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault updated HBASE-26891:
--------------------------------------
Release Note: Adds a new "hbase.client.metrics.scope" config which allows
users to define a custom scope for each Connection's metric instance. The
default scope has also been changed to include the clusterId of the Connection,
which should help differentiate metrics for processes connecting to multiple
clusters. The scope is added to the ObjectName for JMX beans, so can be used to
query for metrics for a particular connection. Using a custom scope might be
useful in cases where you maintain separate Connections for writes vs reads. In
that case you can set the scope appropriately and differentiate metrics for
each.
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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.7#820007)
