[
https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163978#comment-17163978
]
Michael Stack commented on HBASE-15519:
---------------------------------------
Thanks for the prompt response [[email protected]]
The lossy-count thread spin up seems extreme at least.
How we figure user name of incoming client seems like it could get some
improvement: i.e. instead of 'hbase', perhaps 'hbase.ip' or 'hbase.hostname'...
Metrics have bloated now I look. This is not main offender (though it could
grow to be if lots of users?) but I see between 35-45 MBeans and then between
2M and 3M for the list of all metrics... which seems like a lot.
This looks like a really useful feature but on by default might be a bit much.
Ideal I think would be being able to switch it on when a problem but then off
again given its expense.... But it doesn't seem possible given the way our
metrics work it seems.
Thanks for entertaining my questions.
> Add per-user metrics
> ---------------------
>
> Key: HBASE-15519
> URL: https://issues.apache.org/jira/browse/HBASE-15519
> Project: HBase
> Issue Type: Sub-task
> Components: metrics
> Affects Versions: 1.2.0
> Reporter: Enis Soztutar
> Assignee: Ankit Singhal
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
> Attachments: HBASE-15519.master.003.patch, hbase-15519_v0.patch,
> hbase-15519_v1.patch, hbase-15519_v1.patch, hbase-15519_v2.patch
>
>
> Per-user metrics will be useful in multi-tenant cases where we can emit
> number of requests, operations, num RPCs etc at the per-user aggregate level
> per regionserver. We currently have throttles per user, but no way to monitor
> resource usage per-user.
> Looking at these metrics, operators can adjust throttles, do capacity
> planning, etc per-user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
