[
https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163961#comment-17163961
]
Ankit Singhal commented on HBASE-15519:
---------------------------------------
{quote}Each instance creates an executor which has a single thread to do
lossy-counting. This seems profligate? No?
{quote}
Yes Looks like a miss by me, we could share an executor with more threads and a
non-blocking queue here.
{quote}Does this feature work? I see the unit tests but on a real cluster where
I have many users, in these metrics, the user shows as 'nobody' or 'hbase'...
{quote}
I tested it with few users on my local setup and I was able to see the users
appearing with the right request count when the requests are coming and
disappears as there is no request, Idea was to get only the top users at a
time. Let me recollect my knowledge around lossyCounting and see how the users
are removed.
> 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)
