[
https://issues.apache.org/jira/browse/HBASE-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154905#comment-13154905
]
Hudson commented on HBASE-4809:
-------------------------------
Integrated in HBase-TRUNK #2472 (See
[https://builds.apache.org/job/HBase-TRUNK/2472/])
[jira] [HBASE-4809] Per-CF set RPC metrics
Summary: Porting RPC metrics incremented for each column family set touched by a
request from 0.89-fb.
Test Plan:
Unit tests, 5-node cluster. Observe metrics through JMX.
The current version of patch compiles but no testing done yet.
Reviewers: nspiegelberg, JIRA, Kannan, Karthik
Reviewed By: nspiegelberg
CC: nspiegelberg, mbautin
Differential Revision: 483
nspiegelberg :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/SchemaMetrics.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestMemStore.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreScanner.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/metrics/TestSchemaConfigured.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/metrics/TestSchemaMetrics.java
> Per-CF set RPC metrics
> ----------------------
>
> Key: HBASE-4809
> URL: https://issues.apache.org/jira/browse/HBASE-4809
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
> Assignee: Mikhail Bautin
> Priority: Minor
> Fix For: 0.94.0
>
> Attachments: D483.1.patch, D483.2.patch, D483.3.patch, D483.4.patch,
> D483.5.patch, HBASE-4809.patch, HBASE-4809_Per_CF_set_RPC_metrics.patch
>
>
> Porting per-CF set metrics for RPC times and response sizes from 0.89-fb to
> trunk. For each "mutation signature" (a set of column families involved in an
> RPC request) we increment several metrics, allowing to monitor access
> patterns. We deal with guarding against an explosion of the number of
> metrics in HBASE-4638 (which might even be implemented as part of this JIRA).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira