[
https://issues.apache.org/jira/browse/HBASE-16549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986152#comment-15986152
]
stack commented on HBASE-16549:
-------------------------------
Now I understand which 'description' you were referring to... Yeah, that is
oversight in our new metrics API.
I like this comment:
{code}
63 * NOTE: Please refer to HBASE-9774 and HBASE-14282. Based
on these two issues, HBase is
64 * moving away from using Hadoop's metric2 to having independent
HBase specific Metrics. Use
65 * {@link BaseSourceImpl#registry} to register the new metrics.
66 *
67 * TODO: As of now, Metrics description cannot be added/ registered
with
68 * {@link BaseSourceImpl#registry}. As metric names are unambiguous
but concise, descriptions of
69 * metrics need to be made available to the user somewhere.
{code}
I skimmed this. I think this is a good start. Lets get it in. Waiting on
[~appy] comments....
> Procedure v2 - Add new AM metrics
> ---------------------------------
>
> Key: HBASE-16549
> URL: https://issues.apache.org/jira/browse/HBASE-16549
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2, Region Assignment
> Affects Versions: 2.0.0
> Reporter: Matteo Bertozzi
> Assignee: Umesh Agashe
> Fix For: 2.0.0
>
> Attachments: HBASE-16549-hbase-14614.v1.patch,
> HBASE-16549-hbase-14614.v2.patch
>
>
> With the new AM we can add a bunch of metrics
> - assign/unassign time
> - server crash time
> - grouping related metrics? (how many batch we do, and similar?)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
