[
https://issues.apache.org/jira/browse/HBASE-27466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Victor Li updated HBASE-27466:
------------------------------
Description:
At present, hbase client metrics is per each individual hconnection and with a
pre-configured scope in conf or cluster ID plus connection ID which has
generated hash code as suffix. If a client has more than one connections and
the scope configuration is common among all connections, the metrics might
override each other.
I am proposing connections to share a common metrics object if the connections
have a common configured scope.
If a connection identity is not provided, client metrics will continue working
per hconnection and has a connection ID as it scope. I.e. no behavior change.
was:
At present, hbase client metrics is per each individual hconnection and with a
pre-configured scope in conf or cluster ID plus connection ID which has
generated hash code as suffix. It make the metrics not flexible enough for
monitoring if one hbase cluster has multiple clients serving different
purposes, we may want to monitoring the hbase client metrics for certain
specific clients, each client may have one or more connections.
I am proposing one more attribute to the metrics like connection identity,
making the metrics per connection identity and use this connection
identification as its scope. The connection identity is provided by hbase user.
If a connection identity is not provided, client metrics will continue working
per hconnection and has a connection ID as it scope. I.e. no behavior change.
> hbase client metrics per user specified identity on hconnections.
> -----------------------------------------------------------------
>
> Key: HBASE-27466
> URL: https://issues.apache.org/jira/browse/HBASE-27466
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Victor Li
> Assignee: Victor Li
> Priority: Major
>
> At present, hbase client metrics is per each individual hconnection and with
> a pre-configured scope in conf or cluster ID plus connection ID which has
> generated hash code as suffix. If a client has more than one connections and
> the scope configuration is common among all connections, the metrics might
> override each other.
> I am proposing connections to share a common metrics object if the
> connections have a common configured scope.
> If a connection identity is not provided, client metrics will continue
> working per hconnection and has a connection ID as it scope. I.e. no behavior
> change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
