[ https://issues.apache.org/jira/browse/HBASE-14082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lei Chen updated HBASE-14082: ----------------------------- Attachment: HBASE-14082-v3.patch Updates: 1. moved replica id from metrics name to a separate metric. 2. updated related test > 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, HBASE-14082-v2.patch, > HBASE-14082-v3.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)