[
https://issues.apache.org/jira/browse/HBASE-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889440#action_12889440
]
Gary Helmling commented on HBASE-2838:
--------------------------------------
I'm guessing these would be added in as additional attributes in
o.a.h.h.regionserver.metrics.RegionServerMetrics?
For the metrics values, look at:
o.a.h.h.metrics.MetricsRate
- averaged rate of occurrances per time unit (requests/sec)
o.a.hadoop.metrics.util.MetricsTimeVaryingInt
- counter reset to 0 at end of sample period
o.a.hadoop.metrics.util.MetricsTimeVaryingLong
- same as a long counter
o.a.hadoop.metrics.util.MetricsTimeVaryingRate
- time-based rate reset to 0 at end of sample period (RPC queue time)
These should map pretty well to the values you want to publish. The
time-varying ones also expose min and max values for the sample period (or
since last reset call) as well.
> Replication metrics
> -------------------
>
> Key: HBASE-2838
> URL: https://issues.apache.org/jira/browse/HBASE-2838
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.90.0
>
>
> Replication needs to publish metrics about its performance:
> - WALEdits read, filtered, sent to slave clusters, applied on slaves
> - size of batches sent/received
> - ms spent on reading, sending, applying edits
> This can be done using HadoopMetrics.
> Also we need to publish information not related to performance:
> - size of each HLog queues
> - age of the last replicated edit in each queue
> - time of last successful replication
> These informations can hardly be graphed, but we still need to represent them
> somehow. It has to be accessible by web UI, shell, and other tools in
> general. I don't feel strongly about creating a new public method on HRS's
> interface, and I'm not sure publishing those in ZooKeeper is a good idea
> either (why add another indirection?). Still wondering about a better
> solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
