[
https://issues.apache.org/jira/browse/HBASE-14082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628857#comment-14628857
]
Clay B. commented on HBASE-14082:
---------------------------------
[~eclark] the intention is to provide a way one can get region metrics rolled
up by region server, region, replica, etc. putting it in another bean would not
provide the desired region metrics differentiation by primary/secondary without
having to replicate the whole bean. (Should we version the JMX beans so the JMX
path has a version in it?).
Also, can you elaborate on how the addition of the replica ID would break your
monitoring? I can see you may need to update some string parsing for a new
format but I don't know of anything in the community which parses HBase JMX
data; we use [Hannibal|https://github.com/sentric/hannibal] for example but it
is log based. And for JMX data we use Graphite right now which we would have to
update our string globing patterns for.
Is there any explicit stability promised for the JMX paths too to understand
what options are open for addition of this data?
> Add replica id to JMX metrics names
> -----------------------------------
>
> Key: HBASE-14082
> URL: https://issues.apache.org/jira/browse/HBASE-14082
> Project: HBase
> Issue Type: Improvement
> Components: metrics
> Reporter: Lei Chen
> Assignee: Lei Chen
> Attachments: HBASE-14082-v1.patch
>
>
> Today, via JMX, one cannot distinguish a primary region from a replica. A
> possible solution is to add replica id to JMX metrics names. The benefits may
> include, for example:
> # Knowing the latency of a read request on a replica region means the first
> attempt to the primary region has timeout.
> # Write requests on replicas are due to the replication process, while the
> ones on primary are from clients.
> # In case of looking for hot spots of read operations, replicas should be
> excluded since TIMELINE reads are sent to all replicas.
> To implement, we can change the format of metrics names found at
> {code}Hadoop->HBase->RegionServer->Regions->Attributes{code}
> from
> {code}namespace_<namespace>_table_<tablename>_region_<regionname>_metric_<metricname>{code}
> to
> {code}namespace_<namespace>_table_<tablename>_region_<regionname>_replicaid_<replicaid>_metric_<metricname>{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
