hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6410) Move RegionServer Metrics to metrics2
Date Tue, 16 Oct 2012 00:35:03 GMT

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

Elliott Clark updated HBASE-6410:

    Attachment: HBASE-6410-2.patch

* Removed all old metrics code.
* Removed SchemaConfigured
* Moved lots of atomic longs/ints to use the faster Counter.
* Added back in metrics 2 code.
* Added in the ability to clear the jmx cache
* Made the naming of metrics a little bit more consistent.
* Added histogram metrics for latency on the server level.  
* The per region lever is just counts to save on space and speed.
* Made lots of the stats get calculated in an executor that runs every few seconds.
** Requests per second is a good example of this. 
* Added some metrics per region.
** The naming format for them is:
*** table.MYTABLENAME.stat
** One aggregating metrics source has multiple sudo sources feeding it.  
** This allows us to have dynamic per region metrics with no hash table look up and no string
manipulation after object creation(That is one of the reasons our metrics were so costly).
** These sudo sources also push metrics that the region and store's compute.  If there are
more per region metrics that are needed let me know.
> Move RegionServer Metrics to metrics2
> -------------------------------------
>                 Key: HBASE-6410
>                 URL: https://issues.apache.org/jira/browse/HBASE-6410
>             Project: HBase
>          Issue Type: Sub-task
>          Components: metrics
>    Affects Versions: 0.96.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Blocker
>         Attachments: HBASE-6410-1.patch, HBASE-6410-2.patch, HBASE-6410.patch
> Move RegionServer Metrics to metrics2

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message