[ 
https://issues.apache.org/jira/browse/HBASE-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phabricator updated HBASE-4809:
-------------------------------

    Attachment: D483.5.patch

mbautin updated the revision "[jira] [HBASE-4809] Per-CF set RPC metrics".
Reviewers: nspiegelberg, JIRA, Kannan, Karthik

  My previous bugfix broke TestMemStore and TestStoreScanner. Fixing them by 
setting the showTableName flag explicitly.

REVISION DETAIL
  https://reviews.facebook.net/D483

AFFECTED FILES
  src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
  src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java
  src/main/java/org/apache/hadoop/hbase/regionserver/metrics/SchemaMetrics.java
  src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java
  src/test/java/org/apache/hadoop/hbase/regionserver/TestMemStore.java
  src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreScanner.java
  
src/test/java/org/apache/hadoop/hbase/regionserver/metrics/TestSchemaConfigured.java
  
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
>         Attachments: D483.1.patch, D483.2.patch, D483.3.patch, D483.4.patch, 
> D483.5.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

        

Reply via email to